VLX NameSpace Support

Since BricsCAD V18.2, the LISP engine supports the "VLX NameSpace" feature for DES encrypted LISP files, which allows to isolate LISP symbols (functions, variables) to the scope of the particular, DES encrypted LISP file;
this prevents clashes of same-named LISP symbols between different LISP files and applications.

To use the VLX NameSpace feature, the LISP files needs to be compiled by new DEScoder v2.7 as installed with BricsCAD V18.2;

VLX NameSpace is supported for both "Single File Encryption" as well as for "VLX Container File" projects (.prv), and for "FAS .projects" (multiple Lisp sources encrypted into multiple .des files).

If LISP files compiled by DEScoder v2.7, using the "VLX NameSPace" option are loaded in BricsCAD V18.1 and older, the Lisp files will still work, but without namespace protection (therefore, clashes of same-named symbols might happen !).

For details related to compatibility of DES files created by new DEScoder v2.7 please see DEScoder LISP encryption.

About the "VLX Application Name" :
LDSP and also AutoLISP docs always refer to a "VLX Application" name ... that is in fact the filename of the application file (name.vlx resp. name.des), without the filename extension and without the path.

These VLX NameSpace related LISP functions are currently supported :

Additionally, few outdated, obsolete VLX NameSpace related functions are still supported - but strongly suggested to not be used any more in new LISP application code.