DISASSEMBLE-SIDE-EFFECTDISASSEMBLE says that "if the relevant function is not a compiled function, it is first compiled.". The definition of COMPILE says that "If name is a non-nil symbol, then the compiled-function is installed as the global function definition of the symbol...". Several implementations have taken this to mean that if DISASSEMBLE is passed a symbol which has an uncompiled function definition, then it has the side-effect of (COMPILE 'symbol).DISASSEMBLE compiles a function, it will never install the newly compiled function. (DEFUN F (A) (1+ A))
(EQ (SYMBOL-FUNCTION 'F)
(PROGN (DISASSEMBLE 'F)
(SYMBOL-FUNCTION 'F)))
This code will return T if this proposal is adopted. Some current implementations will return T, some will return NIL.
DISASSEMBLE have surprising side effects, especially for new users.CL installs the compiled definition. Lucid, Symbolics, Xerox, VAX Lisp, and KCL don't install it.DISASSEMBLE is really part of the environment and is probably not called by much, if any user code.DISASSEMBLE will continue to surprise less experienced users.DISASSEMBLE will become the predictable debugging function it was meant to be.DISASSEMBLE was supposed to install the compiled function may find that the language has become a little cleaner.DISASSEMBLE is an environment feature; some question has been raised as to the place and force of environment features in the standard. However, this proposal stands if DISASSEMBLE is part of the standard language.