Successor to eval-when?

[Christopher Fry <cfry@OZ.AI.MIT.EDU>]

    Received: from MC.LCS.MIT.EDU by OZ.AI.MIT.EDU via Chaosnet; 10 Apr 86 04:17-EST
    Received: from SU-AI.ARPA by MC.LCS.MIT.EDU 10 Apr 86 04:16:41 EST
    Received: from C.CS.CMU.EDU by SU-AI.ARPA with TCP; 10 Apr 86  00:50:38 PST
    Received: ID <RAM@C.CS.CMU.EDU>; Thu 10 Apr 86 03:51:25-EST
    Date: Thu, 10 Apr 1986  03:51 EST
    Message-ID: <RAM.12197657052.BABYL@C.CS.CMU.EDU>
    From: Rob MacLachlan <RAM@C.CS.CMU.EDU>
    To:   common-lisp@SU-AI.ARPA
    Subject: Successor to eval-when?


	If anyone has an idea for a replacement to eval-when, speak up.  I
    don't have any idea of anything that would be better.  There seem to
    be two main reasons people are upset with eval-when:
     1] It is currently ill-defined.
     2] It is hard to understand.
    I believe that the first problem is fairly easy to fix; I suspect that
    the second problem is inherent in the nature of the beast.

      Rob
It is also poorly named according to the semantics that people
seem to have agreed upon.