Progress on understanding the compilation of Stringscope
Reporting on the implementation of new commands for Stringscope I noted my confusion on why File Manager building commands such as
(CLEANUP 'STRINGSCOPE) sometimes don't write to a file the compiled Lisp code.
It turns out this occurred when loading Stringscope with
FILESLOAD, which loads a compiled file if available. So, even after modifying the Lisp source, the File Manager somehow skipped the compilation step as it assumed the file was up to date. Loading Stringscope with
LOAD instead, which pulls the source, is usually enough to make
CLEANUP write the compiled file.
It's a step forward. But I still don't understand why
(CLEANUP 'STRINGSCOPE) or
(MAKEFILE 'STRINGSCOPE 'C) don't always compile to a file when the source is edited in memory.
Discuss... Email | Reply @firstname.lastname@example.org