In article <
23a85458-e885-46c6...@googlegroups.com>,
Most defining macros are of the form
(defWHATER <whatever-name> ...)
DEFSTRUCT is the odd man out in this pattern, and I guess the creators
of DEFCLASS didn't want to copy that mistake.
It also may be related to the fact that DEFSTRUCT was originally created
for MACLISP, which didn't have keywords. So there was no way to put
structure options in the body along with the list of slots -- they would
look like slot definitions. But when DEFCLASS was created, we could
depend on the fact that keywords can't be used as slot names, so a list
beginning with a keyword must be a class option rather than a slot
specification.
--
Barry Margolin,
bar...@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***