36.3. Recompilation
Prev | Chapter 36. Extending CLISP | Next

## 36.3. Recompilation

Any change that forces make to remake `lisp.run`, will force recompilation of all `#P".lisp"` files and re-dumping of `lispinit.mem`, which may be time-consuming. This is not always necessary, depending on what kind of change you introduced.

On the other hand, if you change any of the following files:

`constobj.d`
`constsym.d`
`fsubr.d`
`subr.d`
`subrkw.d`

your `lispinit.mem` will have to be re-dumped.

### Warning

If you change the signature of any system function mentioned in the `FUNTAB` arrays in file `eval.d`, all the `#P".fas"` files will become obsolete and will need to be recompiled. You will need to add a note to that effect to the `src/NEWS` file and augment the object `version` in file `constobj.d`. Please try to avoid this as much as possible.

| These notes document CLISP version 2.45 | Last modified: 2008-05-14

Enter your search termsSubmit search form
Webclisp.cons.orgclisp.podval.orgwww.lisp.org

Prev | Up | Next
36.2. Adding a built-in variable | Home | Chapter 37. The CLISP bytecode specification