References: Draft 8.81, p.4-15
Draft 8.81, Glossary
Edit history: Version 1, 28-Mar-91, Kim Barrett
Status: Proposal AFFIRM was approved at the 3/91 meeting
It was recently noted that the 8.81 draft defines parameter specializer names
to include class objects. This inclusion seems to be without basis in
decisions made by X3J13, and the editor believes it to be an editorial error.
However, there has been previous discussion of exactly this question on the
clos mailing list, in which the general consensus seemed to be that class
objects should be permitted as parameter specializer names.
Affirm the wording in the 8.81 draft on page 4-15, which states that a class
object may be used as a parameter specializer name.
(defclass foo-class () ())
(defmethod foo-method ((x #.(find-class foo-class))) x)
Not affirming the draft's wording would make parameter specializer names
inconsistent with other parts of the language, since the use of class objects
and class names are generally interchangeable when used as type specifiers.
The draft already says this.
Lucid 4.0 and Chestnut's Lisp to C translator support this.
Several other implementations probably also support this.
Cost to Implementors:
Cost to Users:
None. This is an upwardly compatible change.
Cost of non-adoption:
Some applications may already depend on this. In the mail discussion of this
question it was mentioned that CLIM may be using class objects as parameter
None if accepted, since the draft already contains the necessary words.
Avoiding inconsistancy regarding the distinction between class objects and
class names when used as type specifiers is more esthetic.