[no subject]

[Philip E. Agre <AGRE at MIT-AI>]

In zwei in System 79.31, ZMail 40.7, Remote-File 2.0, LMFILE-Remote 5.3,
Knowledge-Based-Editor 2.2, microcode 849, Sorcerer's Apprentice, on Lisp Machine Twenty-two:

Compile Buffer Changed Functions is not very smart about figuring out
what needs to be compiled.  For example, enter a fresh editor buffer,
type 

(defun foo (x) (- x 2))
(defun bar (y) (+ y 2))

then do Compile Buffer Changed Functions.  No functions are
compiled.  Then move to the end of the foo line, do C-B C-B
Rubout 3, then do Compile Buffer Changed Functions.  No
functions are compiled.  Then do Evaluate Buffer, then C-N
Rubout 4, and Compile Buffer Changed Functions compiles bar.
But then do M-< C-U C-K (defun quux (z) (- z 5)) and Compile
Buffer Changed Functions, and it claims to compile foo. There
are many more strange behaviors that I have come across but have
not been able to characterize sufficiently well to report.
These include functions claiming to be compiled but not changing
their behavior and functions not being compiled even though they
were changed.  I suspect that this has to do with the
"sectioning" of buffers, a process I don't understand (and can't
figure out a good way of doing), but I don't know.  (These
strange behaviors are not restricted to cadr-22, but I have not
run the particular example I gave on another machine, or under
systems 80 or 204.)