You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I edit PRINT-ALL-DOCUMENTATION in CMLEXEC, doing a MAKEFILE (or CLEANUP) includes in the new file, a modified copy of the CMLEXECCOMS.
I (LOAD 'CMLEXEC 'PROP) before editing the function.
How should this be done to avoid ending up with the modified COMS?
The modification seems to be happening during the MAKEFILE.
The text was updated successfully, but these errors were encountered:
What I remember is that this is expected behavior if the MAKEFILE encounters a misspelled filecom and spell corrects, or if NLAML NLAMA LAMA are not set because the appearance of functions on those lists determine in some Interlisp implementations how calls are compiled. This is old behavior from Interlisp-10 but LAMA and NLAMBDAs are compiled differently than calls to LAMLs.
I hope this is all in the IRM but I haven't checked. What is the change to the fileCOMS that you notice?
i'm not sure if the CL:COMPILE-FILE DFASL compiler vs. BCOMPL/TCOMPL and CL:EFUN vs DEFINEQ of CL:LAMBDA, and &KEY &REST but at some point the behavior is intended if unexpected.
If I edit
PRINT-ALL-DOCUMENTATION
in CMLEXEC, doing a MAKEFILE (or CLEANUP) includes in the new file, a modified copy of theCMLEXECCOMS
.I
(LOAD 'CMLEXEC 'PROP)
before editing the function.How should this be done to avoid ending up with the modified COMS?
The modification seems to be happening during the MAKEFILE.
The text was updated successfully, but these errors were encountered: