Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
AutoLISP
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==History== AutoLISP was derived from an early version of [[XLISP]], which was created by David Betz.<ref>{{cite web |url=http://ronleigh.com/autolisp/ahistory.htm |title=History of AutoLISP|archive-url=https://web.archive.org/web/20250126052454/http://ronleigh.com/autolisp/ahistory.htm|archive-date=2025-01-26|url-status=dead|access-date=2025-03-17}}</ref> The language was introduced in AutoCAD Version 2.18 in January 1986, and continued to be enhanced in successive releases up to release 13 in February 1995. After that, its development was neglected by [[Autodesk]] in favor of more fashionable development environments like [[Visual Basic for Applications]] (VBA), [[.NET Framework]], and [[ObjectARX]]. However, it has remained AutoCAD's main user customizing language. ''Vital-LISP'', a considerably enhanced version of AutoLISP including an [[integrated development environment]] (IDE), [[debugger]], [[compiler]], and [[ActiveX]] support, was developed and sold by third-party developer Basis Software. Vital LISP was a superset of the existing AutoLISP language that added VBA-like access to the AutoCAD object model, reactors (event handling for AutoCAD objects), general ActiveX support, and some other general Lisp functions. Autodesk purchased this, renamed it ''Visual LISP'', and briefly sold it as an add-on to AutoCAD release 14 released in May 1997. It was incorporated into AutoCAD 2000 released in March 1999, as a replacement for AutoLISP. Since then, [[Autodesk]] has ceased major enhancements to Visual LISP and focused more effort on VBA and [[.NET]], and [[C++]]. {{As of|2014|January|31|df=US}}, Autodesk ended support for VBA versions before 7.1, as part of a long-term process of changing from VBA to .NET for user customizing.<ref name=vba>{{cite web |url=http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=770215 |title=Microsoft Visual Basic for Applications Module FAQ |access-date=14 April 2014}}</ref><ref name=vbasupport>{{cite web |url=http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/VBA-support-in-AutoCAD-2011.html |title=VBA support in AutoCAD 2011 |access-date=14 April 2014 |archive-url=https://web.archive.org/web/20140415063735/http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/VBA-support-in-AutoCAD-2011.html |archive-date=15 April 2014 |url-status=dead }}</ref> AutoLISP has such a strong following that other [[computer-aided design]] (CAD) application vendors add it to their products. [[Bricscad]], [[IntelliCAD]], DraftSight and others have AutoLISP functionality, so that AutoLISP users can consider using them as an alternative to AutoCAD. Most development involving AutoLISP since AutoCAD 2000 is performed within Visual LISP since the original AutoLISP engine was replaced with the Visual LISP engine. There are thousands of utilities and applications that have been developed using AutoLISP or Visual LISP (distributed as LSP, FAS and VLX files).<ref name=bricscad>{{cite web |url=http://www.bricsys.com/en_INTL/bricscad/comparison/ |access-date=14 April 2014 |title=BricsCAD Compare versions |archive-url=https://web.archive.org/web/20140315233311/http://www.bricsys.com/en_INTL/bricscad/comparison/|archive-date=2014-03-15 |url-status=dead }}</ref><ref name=IntelliCAD>{{cite web |url=http://www.intellicad.org/intellicad-features-and-benefits |title=IntelliCAD CAD Platform β Features and Benefits |access-date=14 April 2014}}</ref> {{Lisp}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)