102 lines
5.2 KiB
HTML
102 lines
5.2 KiB
HTML
<!-- Common Lisp HyperSpec (TM), version 7.0 generated by Kent M. Pitman on Mon, 11-Apr-2005 2:31am EDT -->
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>CLHS: Issue CLASS-OBJECT-SPECIALIZER Writeup</TITLE>
|
|
<LINK HREF="../Data/clhs.css" REL="stylesheet" TYPE="text/css" />
|
|
<META HTTP-EQUIV="Author" CONTENT="Kent M. Pitman">
|
|
<META HTTP-EQUIV="Organization" CONTENT="LispWorks Ltd.">
|
|
<LINK REL=TOP HREF="../Front/index.htm">
|
|
<LINK REL=COPYRIGHT HREF="../Front/Help.htm#Legal">
|
|
<LINK REL=DISCLAIMER HREF="../Front/Help.htm#Disclaimer">
|
|
<LINK REL=PREV HREF="../Issues/iss046_w.htm">
|
|
<LINK REL=UP HREF="../Issues/iss047.htm">
|
|
<LINK REL=NEXT HREF="../Issues/iss048_w.htm">
|
|
</HEAD>
|
|
<BODY>
|
|
<H1><A REV=MADE HREF="http://www.lispworks.com/"><IMG WIDTH=80 HEIGHT=65 ALT="[LISPWORKS]" SRC="../Graphics/LWSmall.gif" ALIGN=Bottom></A><A REL=TOP HREF="../Front/index.htm"><IMG WIDTH=237 HEIGHT=65 ALT="[Common Lisp HyperSpec (TM)]" SRC="../Graphics/CLHS_Sm.gif" ALIGN=Bottom></A> <A REL=PREV HREF="../Issues/iss046_w.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Previous]" SRC="../Graphics/Prev.gif" ALIGN=Bottom></A><A REL=UP HREF="../Issues/iss047.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Up]" SRC="../Graphics/Up.gif" ALIGN=Bottom></A><A REL=NEXT HREF="../Issues/iss048_w.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Next]" SRC="../Graphics/Next.gif" ALIGN=Bottom></A></H1>
|
|
|
|
<HR>
|
|
|
|
|
|
|
|
<H2>Issue CLASS-OBJECT-SPECIALIZER Writeup</H2>
|
|
|
|
<PRE><B>Issue:</B> <A HREF="iss047.htm">CLASS-OBJECT-SPECIALIZER</A><P>
|
|
<B>References:</B> Draft 8.81, p.4-15<P>
|
|
Draft 8.81, Glossary<P>
|
|
88-002R<P>
|
|
<B>Category:</B> CHANGE<P>
|
|
<B>Edit history:</B> Version 1, 28-Mar-91, Kim Barrett<P>
|
|
<B>Status:</B> Proposal AFFIRM was approved at the 3/91 meeting<P>
|
|
<P>
|
|
<B>Problem description:<P>
|
|
</B><P>
|
|
It was recently noted that the 8.81 draft defines parameter specializer names<P>
|
|
to include <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A> objects. This inclusion seems to be without basis in<P>
|
|
decisions made by X3J13, and the editor believes it to be an editorial error.<P>
|
|
<P>
|
|
However, there has been previous discussion of exactly this question on the<P>
|
|
clos mailing list, in which the general consensus seemed to be that <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A><P>
|
|
objects should be permitted as parameter specializer names.<P>
|
|
<P>
|
|
<B>Proposal (CLASS-OBJECT-SPECIALIZER:AFFIRM):<P>
|
|
</B><P>
|
|
Affirm the wording in the 8.81 draft on page 4-15, which states that a <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A><P>
|
|
object may be used as a parameter specializer name.<P>
|
|
<P>
|
|
<B>Examples:<P>
|
|
</B><P>
|
|
(<A REL=DEFINITION HREF="../Body/m_defcla.htm#defclass"><B>defclass</B></A> foo-class () ())<P>
|
|
(<A REL=DEFINITION HREF="../Body/m_defmet.htm#defmethod"><B>defmethod</B></A> foo-method ((x #.(<A REL=DEFINITION HREF="../Body/f_find_c.htm#find-class"><B>find-class</B></A> foo-class))) x)<P>
|
|
<P>
|
|
<B>Rationale:<P>
|
|
</B><P>
|
|
Not affirming the draft's wording would make parameter specializer names<P>
|
|
inconsistent with other parts of the language, since the use of <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A> objects<P>
|
|
and <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A> names are generally interchangeable when used as type specifiers.<P>
|
|
<P>
|
|
The draft already says this.<P>
|
|
<P>
|
|
<B>Current Practice:<P>
|
|
</B><P>
|
|
Lucid 4.0 and Chestnut's Lisp to C translator support this.<P>
|
|
<P>
|
|
Several other implementations probably also support this.<P>
|
|
<P>
|
|
<B>Cost to Implementors:<P>
|
|
</B><P>
|
|
Likely small.<P>
|
|
<P>
|
|
<B>Cost to Users:<P>
|
|
</B><P>
|
|
None. This is an upwardly compatible change.<P>
|
|
<P>
|
|
<B>Cost of non-adoption:<P>
|
|
</B><P>
|
|
Some applications may already depend on this. In the mail discussion of this<P>
|
|
question it was mentioned that CLIM may be using <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A> objects as parameter<P>
|
|
specializer names.<P>
|
|
<P>
|
|
<B>Performance impact:<P>
|
|
</B><P>
|
|
None.<P>
|
|
<P>
|
|
<B>Editorial impact:<P>
|
|
</B><P>
|
|
None if accepted, since the draft already contains the necessary words.<P>
|
|
<P>
|
|
<B>Esthetics:<P>
|
|
</B><P>
|
|
Avoiding inconsistancy regarding the distinction between <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A> objects and<P>
|
|
<A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A> names when used as type specifiers is more esthetic.<P>
|
|
<P>
|
|
<B>Discussion:<P>
|
|
</B><P>
|
|
</PRE>
|
|
<HR>
|
|
|
|
<A REL=NAVIGATOR HREF="../Front/StartPts.htm"><IMG WIDTH=80 HEIGHT=40 ALT="[Starting Points]" SRC="../Graphics/StartPts.gif" ALIGN=Bottom></A><A REL=TOC HREF="../Front/Contents.htm"><IMG WIDTH=80 HEIGHT=40 ALT="[Contents]" SRC="../Graphics/Contents.gif" ALIGN=Bottom></A><A REL=INDEX HREF="../Front/X_Master.htm"><IMG WIDTH=80 HEIGHT=40 ALT="[Index]" SRC="../Graphics/Index.gif" ALIGN=Bottom></A><A REL=INDEX HREF="../Front/X_Symbol.htm"><IMG WIDTH=80 HEIGHT=40 ALT="[Symbols]" SRC="../Graphics/Symbols.gif" ALIGN=Bottom></A><A REL=GLOSSARY HREF="../Body/26_a.htm"><IMG WIDTH=80 HEIGHT=40 ALT="[Glossary]" SRC="../Graphics/Glossary.gif" ALIGN=Bottom></A><A HREF="../Front/X3J13Iss.htm"><IMG WIDTH=80 HEIGHT=40 ALT="[Issues]" SRC="../Graphics/Issues.gif" ALIGN=Bottom></A><BR>
|
|
|
|
<A REL=COPYRIGHT HREF="../Front/Help.htm#Legal"><I>Copyright 1996-2005, LispWorks Ltd. All rights reserved.</I></A><P>
|
|
</BODY>
|
|
</HTML>
|