<?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: in VBA Forum</title>
    <link>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348062#M78068</link>
    <description>Without lisp VB/VBA can not do everything in AC. Lisp can do everything in&lt;BR /&gt;
AC. Some prime examples are the draworder, and trim command. With VB/VBA you&lt;BR /&gt;
can not trim, you would need to recalc the points and reassign them to the&lt;BR /&gt;
object. Lisp can trim entities. Without the sendcommand in vba you would&lt;BR /&gt;
never be able to change the draworder of entities. VB/VBA can not create AC&lt;BR /&gt;
commands IE in lisp one could (defun c:junk ()...) and the user could type&lt;BR /&gt;
junk at the command prompt and execute the command. To do this in VB/VBA one&lt;BR /&gt;
must first do (defun c:junk () (vl-vbarun "vbaSub")). Only then could the&lt;BR /&gt;
user type in junk at the command prompt and execute the sub. I learned to&lt;BR /&gt;
write lisp first (years ago), but enjoy writing vb/vba now. I feel the&lt;BR /&gt;
writing in vb/vba and using defun's to create command's makes me a better&lt;BR /&gt;
programmer because I continue to develop my vb/vba skills, which there are&lt;BR /&gt;
many more places to write vb than lisp.&lt;BR /&gt;
&lt;BR /&gt;
HTH&lt;BR /&gt;
&lt;BR /&gt;
Chris&lt;BR /&gt;
&lt;BR /&gt;
"Andy &amp;amp; Starr" &lt;ANDYRACE&gt; wrote in message&lt;BR /&gt;
news:3C3F856D.EF87C9CC@bellsouth.net...&lt;BR /&gt;
&amp;gt; &amp;gt; Hi all I am looking to see what VBA can do that cannot be done in Lisp&lt;BR /&gt;
&amp;gt; &amp;gt; or VisualLisp. I know about the dialog box differences already. I am&lt;BR /&gt;
&amp;gt; &amp;gt; looking for non dialog box functionality.&lt;BR /&gt;
&amp;gt;&lt;BR /&gt;
&amp;gt;   When the task is manipulating autocad, the two languages have nearly&lt;BR /&gt;
&amp;gt; identical capabilities. If the task is a routine to operate on autocad&lt;BR /&gt;
&amp;gt; alone, lisp would probably be the tool of choice for an accomplished&lt;BR /&gt;
&amp;gt; lisp programer. VBA provides access to any activeX enable program and&lt;BR /&gt;
&amp;gt; the operating system, making it suitable for a project that interfaces&lt;BR /&gt;
&amp;gt; with a database or spread sheet. As you mentioned, vba includes rich&lt;BR /&gt;
&amp;gt; interface capabilities. An important aspect of adesk's inclusion of an&lt;BR /&gt;
&amp;gt; object model in cad was not just providing the cad user with vba, but&lt;BR /&gt;
&amp;gt; providing VB programers access to cad.&lt;BR /&gt;
&amp;gt;&lt;/ANDYRACE&gt;</description>
    <pubDate>Fri, 11 Jan 2002 17:02:09 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2002-01-11T17:02:09Z</dc:date>
    <item>
      <title>What Can VBA do that Lisp cannot</title>
      <link>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348060#M78066</link>
      <description>Hi all I am looking to see what VBA can do that cannot be done in Lisp or VisualLisp. I know about the dialog box differences already. I am looking for non dialog box functionality.</description>
      <pubDate>Fri, 11 Jan 2002 10:17:19 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348060#M78066</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2002-01-11T10:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: What Can VBA do that Lisp cannot</title>
      <link>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348061#M78067</link>
      <description>&amp;gt; Hi all I am looking to see what VBA can do that cannot be done in Lisp&lt;BR /&gt;
&amp;gt; or VisualLisp. I know about the dialog box differences already. I am&lt;BR /&gt;
&amp;gt; looking for non dialog box functionality.&lt;BR /&gt;
&lt;BR /&gt;
  When the task is manipulating autocad, the two languages have nearly&lt;BR /&gt;
identical capabilities. If the task is a routine to operate on autocad&lt;BR /&gt;
alone, lisp would probably be the tool of choice for an accomplished&lt;BR /&gt;
lisp programer. VBA provides access to any activeX enable program and&lt;BR /&gt;
the operating system, making it suitable for a project that interfaces&lt;BR /&gt;
with a database or spread sheet. As you mentioned, vba includes rich&lt;BR /&gt;
interface capabilities. An important aspect of adesk's inclusion of an&lt;BR /&gt;
object model in cad was not just providing the cad user with vba, but&lt;BR /&gt;
providing VB programers access to cad.</description>
      <pubDate>Fri, 11 Jan 2002 16:38:05 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348061#M78067</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2002-01-11T16:38:05Z</dc:date>
    </item>
    <item>
      <title>Re:</title>
      <link>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348062#M78068</link>
      <description>Without lisp VB/VBA can not do everything in AC. Lisp can do everything in&lt;BR /&gt;
AC. Some prime examples are the draworder, and trim command. With VB/VBA you&lt;BR /&gt;
can not trim, you would need to recalc the points and reassign them to the&lt;BR /&gt;
object. Lisp can trim entities. Without the sendcommand in vba you would&lt;BR /&gt;
never be able to change the draworder of entities. VB/VBA can not create AC&lt;BR /&gt;
commands IE in lisp one could (defun c:junk ()...) and the user could type&lt;BR /&gt;
junk at the command prompt and execute the command. To do this in VB/VBA one&lt;BR /&gt;
must first do (defun c:junk () (vl-vbarun "vbaSub")). Only then could the&lt;BR /&gt;
user type in junk at the command prompt and execute the sub. I learned to&lt;BR /&gt;
write lisp first (years ago), but enjoy writing vb/vba now. I feel the&lt;BR /&gt;
writing in vb/vba and using defun's to create command's makes me a better&lt;BR /&gt;
programmer because I continue to develop my vb/vba skills, which there are&lt;BR /&gt;
many more places to write vb than lisp.&lt;BR /&gt;
&lt;BR /&gt;
HTH&lt;BR /&gt;
&lt;BR /&gt;
Chris&lt;BR /&gt;
&lt;BR /&gt;
"Andy &amp;amp; Starr" &lt;ANDYRACE&gt; wrote in message&lt;BR /&gt;
news:3C3F856D.EF87C9CC@bellsouth.net...&lt;BR /&gt;
&amp;gt; &amp;gt; Hi all I am looking to see what VBA can do that cannot be done in Lisp&lt;BR /&gt;
&amp;gt; &amp;gt; or VisualLisp. I know about the dialog box differences already. I am&lt;BR /&gt;
&amp;gt; &amp;gt; looking for non dialog box functionality.&lt;BR /&gt;
&amp;gt;&lt;BR /&gt;
&amp;gt;   When the task is manipulating autocad, the two languages have nearly&lt;BR /&gt;
&amp;gt; identical capabilities. If the task is a routine to operate on autocad&lt;BR /&gt;
&amp;gt; alone, lisp would probably be the tool of choice for an accomplished&lt;BR /&gt;
&amp;gt; lisp programer. VBA provides access to any activeX enable program and&lt;BR /&gt;
&amp;gt; the operating system, making it suitable for a project that interfaces&lt;BR /&gt;
&amp;gt; with a database or spread sheet. As you mentioned, vba includes rich&lt;BR /&gt;
&amp;gt; interface capabilities. An important aspect of adesk's inclusion of an&lt;BR /&gt;
&amp;gt; object model in cad was not just providing the cad user with vba, but&lt;BR /&gt;
&amp;gt; providing VB programers access to cad.&lt;BR /&gt;
&amp;gt;&lt;/ANDYRACE&gt;</description>
      <pubDate>Fri, 11 Jan 2002 17:02:09 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348062#M78068</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2002-01-11T17:02:09Z</dc:date>
    </item>
    <item>
      <title>Re:</title>
      <link>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348063#M78069</link>
      <description>Chris Tryon wrote:&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt; Without lisp VB/VBA can not do everything in AC.&lt;BR /&gt;
&lt;BR /&gt;
I agree, as the object model matures hopfully it will continue to improve.&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt; Lisp can do everything in&lt;BR /&gt;
&amp;gt; AC.&lt;BR /&gt;
&lt;BR /&gt;
especially now with all the activeX commands!!!&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt; Some prime examples are the draworder, and trim command. With VB/VBA you&lt;BR /&gt;
&amp;gt; can not trim, you would need to recalc the points and reassign them to the&lt;BR /&gt;
&amp;gt; object.&lt;BR /&gt;
&lt;BR /&gt;
to the user, is this not a trim?&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt; Lisp can trim entities. Without the sendcommand in vba you would&lt;BR /&gt;
&amp;gt; never be able to change the draworder of entities. VB/VBA can not create AC&lt;BR /&gt;
&amp;gt; commands IE in lisp one could (defun c:junk ()...) and the user could type&lt;BR /&gt;
&amp;gt; junk at the command prompt and execute the command. To do this in VB/VBA one&lt;BR /&gt;
&amp;gt; must first do (defun c:junk () (vl-vbarun "vbaSub")). Only then could the&lt;BR /&gt;
&amp;gt; user type in junk at the command prompt and execute the sub.&lt;BR /&gt;
&lt;BR /&gt;
autolisp's access to the lisp interpreter, the command line interpreter, and the&lt;BR /&gt;
drawing database make it's power as a  tool for manipulating autocad&lt;BR /&gt;
unparalleled.&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt; I learned to&lt;BR /&gt;
&amp;gt; write lisp first (years ago), but enjoy writing vb/vba now. I feel the&lt;BR /&gt;
&amp;gt; writing in vb/vba and using defun's to create command's makes me a better&lt;BR /&gt;
&amp;gt; programmer&lt;BR /&gt;
&lt;BR /&gt;
all the options make life good for a guy who codes&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt; because I continue to develop my vb/vba skills, which there are&lt;BR /&gt;
&amp;gt; many more places to write vb than lisp.&lt;BR /&gt;
&lt;BR /&gt;
Do you mean it's easier to get a job writing VB then lisp?&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt;&lt;BR /&gt;
&amp;gt;&lt;BR /&gt;
&amp;gt; HTH&lt;BR /&gt;
&amp;gt;&lt;BR /&gt;
&amp;gt; Chris</description>
      <pubDate>Fri, 11 Jan 2002 17:21:11 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348063#M78069</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2002-01-11T17:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: What Can VBA do that Lisp cannot</title>
      <link>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348064#M78070</link>
      <description>by the way, when your web site is viewed in 1024 x 768 resolution some&lt;BR /&gt;
of the black text ends up in the dark green part of the background.&lt;BR /&gt;
makes it hard to read.&lt;BR /&gt;
&lt;BR /&gt;
cwanless wrote:&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt; Hi all I am looking to see what VBA can do that cannot be done in Lisp&lt;BR /&gt;
&amp;gt; or VisualLisp. I know about the dialog box differences already. I am&lt;BR /&gt;
&amp;gt; looking for non dialog box functionality.</description>
      <pubDate>Fri, 11 Jan 2002 18:03:43 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348064#M78070</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2002-01-11T18:03:43Z</dc:date>
    </item>
    <item>
      <title>Re:</title>
      <link>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348065#M78071</link>
      <description>Thanks I will probably be redoing the entire web site in the next week or two. Thanks Chad</description>
      <pubDate>Sun, 13 Jan 2002 11:32:52 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vba-forum/what-can-vba-do-that-lisp-cannot/m-p/348065#M78071</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2002-01-13T11:32:52Z</dc:date>
    </item>
  </channel>
</rss>

