[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
issue status, 12/12/88
- To: email@example.com
- Subject: issue status, 12/12/88
- From: firstname.lastname@example.org (Sandra J Loosemore)
- Date: Mon, 12 Dec 88 14:43:03 MST
Here is the summary of the status of our pending issues as of today.
Once again I must ask you to note that we are running out of time
before the January meeting. My effective deadline is the middle of
next week, because that's when I'm going on vacation.
These issues appear to be ready for release.
The following issues are those that I would like to finish up within the
next week or so, with notes on what remains to be done.
The NOTICE condition type hasn't happened yet. I was going to change
references to the NOTICE condition to the STYLE-WARNING condition,
which is a subtype of warning (allowing user condition handlers to use
the MUFFLE-WARNING restart on it to suppress the messages). Any
Pierson indicated he wanted to submit an alternate proposal on this
issue, but hasn't done so. Can/should we go ahead with the current
I've been working on a revised version that is essentially complete
except for information about the CLOS defining macros. The CLOS
people haven't responded to my requests for help. I don't hear from
them, should we release the issue anyway, leaving the CLOS macros for
There's been a suggestion that defining macros should only cause
compile-time side effects at top level, and that (EVAL-WHEN
(COMPILE)...) should be a no-op except at top level. Is this
agreeable to everybody?
Do we really need all three options in the latest writeup?
We need a new draft of this proposal to incorporate the latest
round of discussion. Cris???
If nobody has complaints about the latest writeups, I'll move these
into the "ready for release" category.
The following issues are those which I don't plan to work on myself
until after the January meeting:
Subsumed by CONSTANT-COMPILABLE-TYPES?
Superseded by issue SYNTACTIC-ENVIRONMENT-ACCESS, unless that issue
Still under discussion, no consensus yet
Subsumed by issue COMPILE-FILE-HANDLING-OF-TOP-LEVEL-FORMS
Waiting for revisions (Pitman)
same issue as CONSTANT-COMPILABLE-TYPES
Waiting for resolution of related cleanup issues (DEFPACKAGE,
Waiting for new writeup (Benson)
Waiting for revisions to existing proposal (Pitman)