<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: .Net call or lisp  entget in .NET Forum</title>
    <link>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3034560#M60800</link>
    <description>&lt;P&gt;Use the LSP.&amp;nbsp; If all you need is a Handle, it would be silly to have to load a .dll to replace 3 lsp function calls.&lt;/P&gt;</description>
    <pubDate>Tue, 24 May 2011 17:20:00 GMT</pubDate>
    <dc:creator>chiefbraincloud</dc:creator>
    <dc:date>2011-05-24T17:20:00Z</dc:date>
    <item>
      <title>.Net call or lisp  entget</title>
      <link>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3034446#M60799</link>
      <description>&lt;P&gt;I do not have time to write code to discover which is faster so I wondered if anyone knew.....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Task: To obtain the Handle to an entity as a string to be used in legacy lisp routines.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Which is likely to be faster;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(cdr(assoc 5(entget eName)))﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A call to a .net DLL that returns the handle of the entity eName.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Opinions anyone?&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2011 15:57:34 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3034446#M60799</guid>
      <dc:creator>StormyC</dc:creator>
      <dc:date>2011-05-24T15:57:34Z</dc:date>
    </item>
    <item>
      <title>Re: .Net call or lisp  entget</title>
      <link>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3034560#M60800</link>
      <description>&lt;P&gt;Use the LSP.&amp;nbsp; If all you need is a Handle, it would be silly to have to load a .dll to replace 3 lsp function calls.&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2011 17:20:00 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3034560#M60800</guid>
      <dc:creator>chiefbraincloud</dc:creator>
      <dc:date>2011-05-24T17:20:00Z</dc:date>
    </item>
    <item>
      <title>Re: .Net call or lisp  entget</title>
      <link>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3035030#M60801</link>
      <description>&lt;P&gt;Agree, however, I already load a .net DLL that replaces other legacy routines - so the loading of the DLL isnt&amp;nbsp;an issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obtaining a handle occurs hundreds of times - so - question still stands... Lisp or .Net. =D&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;....can't rewrite all of the lisp routines in .net yet&amp;nbsp;because of time constraints.&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2011 22:06:10 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3035030#M60801</guid>
      <dc:creator>StormyC</dc:creator>
      <dc:date>2011-05-24T22:06:10Z</dc:date>
    </item>
    <item>
      <title>Re: .Net call or lisp  entget</title>
      <link>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3035048#M60802</link>
      <description>&lt;P&gt;I still say, for this case, use the LSP.&amp;nbsp; For routines that you are converting from LSP to .NET, I would go ahead and convert them completely to use all .NET and no LSP, but for the particular case you presented, I do not think there would be a benefit to a .NET function to return the handle as a string.&amp;nbsp; On the contrary, I think it would result in more CPU instructions and memory read/writes&amp;nbsp;rather than less.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2011 22:29:29 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3035048#M60802</guid>
      <dc:creator>chiefbraincloud</dc:creator>
      <dc:date>2011-05-24T22:29:29Z</dc:date>
    </item>
    <item>
      <title>Re: .Net call or lisp  entget</title>
      <link>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3035050#M60803</link>
      <description>&lt;P&gt;The previous answer still stands &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp; A couple of hundred calls to extracting a handle from an (entget...) list?&amp;nbsp; That won't get any faster with .NET.&amp;nbsp; If speed is critical and you keep pulling the same handles,&amp;nbsp;then consider some optimization such as caching the handle values alongside the entity codes in a list of dotted pairs e.g. (&amp;lt;Ecode&amp;gt; . "Handle").&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2011 22:29:39 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3035050#M60803</guid>
      <dc:creator>dgorsman</dc:creator>
      <dc:date>2011-05-24T22:29:39Z</dc:date>
    </item>
    <item>
      <title>Re: .Net call or lisp  entget</title>
      <link>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3035344#M60804</link>
      <description>&lt;P&gt;Thanks for the responses guys, very much appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2011 07:47:15 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/net-forum/net-call-or-lisp-entget/m-p/3035344#M60804</guid>
      <dc:creator>StormyC</dc:creator>
      <dc:date>2011-05-25T07:47:15Z</dc:date>
    </item>
  </channel>
</rss>

