So were does one go after AutoLISP? VB(A), C++, Perl, etc.......
I have been pondering this issue for some time now. In all likely hood VB(A) would be the right choice considering that I work with ACAD and many other Windows programs that make use of it. The problem is that ties you to the Windows family of OS's, what about all the *nix OS's? Then there is the fact that you have to _pay_ for the compiler if you want stand-alone apps, it's not cheap either. For about the past four years I have become a big fan of the open source movement. I like the idea and the programs it produces. For example, take a look at
http://gnuwin32.sourceforge.net/ . So that takes us to C++, a very high level language with a high level learning curve to go with it. Getting the tools I need to produce C++ apps on Windows is a piece of cake, I just point by browser to
http://www.mingw.org . The apps can be ran on many different OS's, but would I write such an app? Of course with C++ I can still write apps for ACAD, albeit somewhat more difficult to do then with AutoLISP. So maybe Perl is the answer? It's a higher level language, it's open source and it can be run on a host of OS's. Plus it's interpretive so I can test it right on the command line like I can do with lisp. I can't use it for ACAD, but I can use it for a plethora of other things, like web applications, database apps or just plain old stand-alone apps to help me get my job done. My job, the bottom line. My job is drafting, not programming. If I invest all the time in learning another language can I make money with, or will it just be a hobby? Will I ever be good enough to move from drafting to programming? Will I want to? Oh wait, what about Python!
perls, pythons and bears oh my! .....................So here I sit, still pondering these many questions. *sigh*