Conformance Model

clautolisp should distinguish at least:

• a core AutoLISP profile,
• an AutoCAD-oriented profile,
• a BricsCAD-oriented profile,
• strict and lax acceptance modes,
• selectable host-environment profiles independent from the native OS.

When an AutoLISP or Visual LISP function family is specified as a wrapper over an underlying host API that is documented elsewhere, the underlying API documentation is part of the normative reference corpus for that family, subject to the calling conventions and restrictions documented by the AutoLISP layer.

This applies in particular to:

• vla-* wrappers over the AutoCAD ActiveX object model,
• vlax-* property, method, variant, safearray, and object-creation functions that expose COM / OLE Automation semantics.

It does not follow that every Windows-only or Visual LISP extension function is merely a generic foreign-function binding; some families, such as vlr-* reactors, remain primarily specified by Autodesk's own AutoLISP / ActiveX documentation.