[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: call-next-method incoherency

    Date: Thu, 3 Aug 89 10:56 PDT
    From: Gregor.pa@Xerox.COM

    It would be nice to have a one or two page list of all the changes that
    have been made to CLOS since we voted 88-002R.  Something that collects
    up, in one place, everything that will be different about what appears
    in the draft standard from 88-002R.

    Does one of us already have such a list?

I don't, although I did make a list of all the cleanup issues that appear
to affect CLOS, which is enclosed below.  I believe changes like this are
supposed to be flagged in the draft of the Common Lisp specification, so
a list could be constructed that way.  The one or two that I did were
mailed to this mailing list.

This is the list of X3J13 issues I found that affect CLOS.  I can't
prove that I didn't miss any.

There should be one saying that FUNCTION, HASH-TABLE, etc. have been made
into classes, but I couldn't find it.  Maybe they forgot to do that.
However, the draft ANSI CL spec does have these as classes.

CLOS-MACRO-COMPILATION  should be no impact, but be careful about DEFINE-METHOD-COMBINATION
COMPILE-FILE-HANDLING-OF-TOP-LEVEL-FORMS  the CLOS part was removed by amendment, so ignore this
DATA-TYPES-HIERARCHY-UNDERSPECIFIED, FUNCTION-TYPE -- just background
DESCRIBE-UNDERSPECIFIED
FUNCTION-NAME  probably does not contradict 88-002R, but check it
LOAD-OBJECTS
REAL-NUMBER-TYPE
SYMBOL-MACROLET-DECLARE
SYMBOL-MACROLET-SEMANTICS
SYNTACTIC-ENVIRONMENT-ACCESS -- as it relates to SYMBOL-MACROLET
TYPE-OF-UNDERCONSTRAINED
UNDEFINED-VARIABLES-AND-FUNCTIONS