Hello,
when developing using slime I often find myself hindered by a "dirty" image, and falling back to using a manual "clean" compile externally.
A typical example is wanting to use B:X in A, but having forgot to export X in B. Compilation of A results in the compiler interning X in A. So now I have to manually unintern the symbol in order to get A to compile, using the symbol from B.
Other situations similar in nature have arissen.
The cause is obvious; but my question is whether anybody uses any particular 'tricks' or procedures to avoid issues like this?
Peter Schuller peter.schuller@infidyne.com writes:
The cause is obvious; but my question is whether anybody uses any particular 'tricks' or procedures to avoid issues like this?
Running the inspector on a package is good for rescue. It knows how to unintern symbols for example.
* Luke Gorrie (luke@synap.se) [050807 17:13]:
Peter Schuller peter.schuller@infidyne.com writes:
The cause is obvious; but my question is whether anybody uses any particular 'tricks' or procedures to avoid issues like this?
Running the inspector on a package is good for rescue. It knows how to unintern symbols for example.
Or you could just delete the offending packages and re-compile them if there's a bunch of these problems.
--larry
-
Larry D'Anna -
Luke Gorrie -
Peter Schuller