Will Lisp Ever Die?... & what of VLIDE?

[mdhutchinson]

I've been doing lisp for quite sometime now... perhaps 25+ years.

it's been a long time since Autodesk made any improvement to access AutoCAD's database via lisp, or for that matter to lisp it self.

... and its been along time since Autodesk made any improvements to VLIDE... perhaps they never have since they acquired VLisp from its creator. (anyone recall who that was?)

... however, I am wondering what the opinion is.

Will Lisp for AutoCAD never die?

[Anonymous]

Will Lisp for AutoCAD never die?

Since most of the AutoCAD commands are created using lisp, it should be around a while longer yet. As far as I know, all the EXPRESS TOOLS are in lisp. Things in AutoCAD don't tend to die anyhow, they just get left in limbo, unimproved yet not discontinued. Witness diesel code, it still works but hasn't been developed since the ninety's. Fields took over. It would take a huge investment to recode all the commands using a different programming language.

[paullimapa]

Visual Lisp according to https://en.wikipedia.org/wiki/AutoLISP was called Vital-Lisp & originally developed by Basis Software

And I agree with the other poster.  AutoLisp, Visual Lisp along with Dialog Control Language will be around as long as AutoCAD supports their code.

I don't see Autodesk making a drastic decision to stop allowing this language to access their full blown AutoCAD product any time soon.

Area Object Link | Attribute Modifier | Dwg Setup | Feet-Inch Calculator
Layer Apps | List on Steroids | VP Zoom Scales | Exchange App Store

[stevor]

The story of Autocad, and autolisp,

is still on the web, from the horse's mouth:

https://www.fourmilab.ch/autofile/www/autofile.html

That contains the reasons for selecting 'Lisp' and

for making an easy to code language: time.

Other CAD makers were making PC versions,

and already had lots of 'tools.'

User made tools were autodesk's only way

to stay in the game.

And, as the CPUs became faster, the speed

of the Lisp code became  insignificant to most.

To most, code writing time is the big cost, your time.

Autodesk would love to lose Autolisp to something

they can have more income, but the big buyers

have based selection on cheap code writing,

and cheap tools, so the lisp has persisted, so far.

[Anonymous]

hi There, Thanks for posting This

I sure hope LISP never dies (& me, Too).

say, I just now downloaded Fusion360, 20 minutes ago, so where

are They hiding the AutoLISP functionality at? I am still Looking for it.

will "old"" AutoLISP still work with This current environment in Fusion360?

or is There a re-write required To make it work with This version of Fusion360?

are There different versions of Fusion360 or is it more Like HTML now, where it is versionless?

sorry To ask so many Questions up front, I have about 30,000 hours using Autocad

both 2d & 3d but about 10 minutes using Fusion360. my email is 2dcd2b3d@.......

I have a job waiting for me as soon as I can get my head around This program.

This is the best combination of SolidWorks and Autocad 3d I have seen so far yet.

I started with the Autocad version That was just b4 Release 9.0 (2.64 ?? maybe)

This is so great. I am "officially" retired. I was tired last week & I am re-tired This week

but now I got sum Thing To Look forward To do each day. I am so glad That I finally found This place.

I got a Ton of AutoLISP files, but The best Idea I came up with was To define commands as <  (defun C:00 (command ".save") () )

You can make all of your command Aliases as Numeric. I use a right mouse Left-handed without resetting any of the button parameters

so I can use any mouse Left-handed while my right-hand is over the Numeric keypad. This is more efficient (for me at Least) To do

do Numeric command selection, Then, whatever the Numeric Input for That command is easily To do. just an Idea,

but This AutoLISP numeric command Input seems To be versionless. MENUs are so **** slow. (2nd edit: note: **** = d@mn)

I guess I will find out soon enough whether This will work or not. as soon as I can find the LISP Loader

I can uploadhere or sumwhere or send You this Lisp, "num-keys.lsp" I have not used it for several Years

I am sure making it into an open source LISP routine would greatly improve any functionality, if others can make more edits to it.

**

Thanks, any comments, observations, assistance and/or suggestions are greatly appreciated.

**

Randy (just add coffee)

2dcd2b3d@gmail.com