In the rare cases when you really need to modify CLISP internals and add a truly built-in function, you should read the CLISP sources for inspiration and enlightenment, choose a file where your brand-new built-in function should go to, and then ...
LISPFUN
form and the implementation there;LISPFUN header to
file subr.d;constsym.d in the appropriate package
(probably “EXT”, if there is no specific package);
subrkw.d and you must make sure that the
keyword symbols are declared in constsym.d;
init.lisp;subr.d, subrkw.d and fsubr.d) are in sync.Be very careful with the GC-unsafe functions! Always remember about GC-safety!
These instructions are intentionally terse - you are encouraged to use modules and/or “FFI” instead of adding built-ins directly.
| These notes document CLISP version 2.45 | Last modified: 2008-05-14 |