Re: Issue EVAL-WHEN-NON-TOP-LEVEL, v2

[cperdue@Sun.COM (Cris Perdue)]

Sandra has to be right -- I was confused about what my example would
do.  Well, I'm not giving up yet.  Here is a different example.
Suppose we have code something like:

(eval-when (load)
  (eval-when (compile load eval)
    (some-action)))
    
This might come in a form such as:

(eval-when (load)
  (def-xxx-macro frob (x) ... ))
  
where def-xxx-macro expands into an eval-when.

I claim that this case, as described in CLtL, does "some-action" at
compile-time despite the request of the user of def-xxx-macro and
despite appearances.  So once again, does anyone know
of reasons why the inner EVAL-WHEN should in effect override
the outer one?
				-Cris