I have received multiple bug reports that relate to this:
https://www.lispworks.com/documentation/HyperSpec/Body/11_abab.htm
It states that a whole slew of things involving external symbols from the COMMON-LISP package are "undefined".
#79 is an example of one of these violations, but there are others, such as #68.
In general, the violations cause no problems when using Lisp-Binary on open-source implementations of Common Lisp, which is why they weren't detected during development.
Commercial implementations tend to check for and disallow such violations. The only workable solution is to remove or rewrite code that invokes undefined behavior. I'll have no tool assistance on this: SBCL doesn't even issue any warnings about that code, so although I'll close this issue after I've fixed known instances of this problem and looked for more, some instances of this problem may escape detection.
I have received multiple bug reports that relate to this:
https://www.lispworks.com/documentation/HyperSpec/Body/11_abab.htm
It states that a whole slew of things involving external symbols from the
COMMON-LISPpackage are "undefined".#79 is an example of one of these violations, but there are others, such as #68.
In general, the violations cause no problems when using Lisp-Binary on open-source implementations of Common Lisp, which is why they weren't detected during development.
Commercial implementations tend to check for and disallow such violations. The only workable solution is to remove or rewrite code that invokes undefined behavior. I'll have no tool assistance on this: SBCL doesn't even issue any warnings about that code, so although I'll close this issue after I've fixed known instances of this problem and looked for more, some instances of this problem may escape detection.