1
0
Fork 0
cl-sites/HyperSpec-7-0/HyperSpec/Issues/iss154_w.htm
2024-04-01 10:24:07 +02:00

144 lines
7.8 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 EXTENSIONS-POSITION 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/iss153_w.htm">
<LINK REL=UP HREF="../Issues/iss154.htm">
<LINK REL=NEXT HREF="../Issues/iss155_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/iss153_w.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Previous]" SRC="../Graphics/Prev.gif" ALIGN=Bottom></A><A REL=UP HREF="../Issues/iss154.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Up]" SRC="../Graphics/Up.gif" ALIGN=Bottom></A><A REL=NEXT HREF="../Issues/iss155_w.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Next]" SRC="../Graphics/Next.gif" ALIGN=Bottom></A></H1>
<HR>
<H2>Issue EXTENSIONS-POSITION Writeup</H2>
<PRE><B>Issue:</B> <A HREF="iss154.htm">EXTENSIONS-POSITION</A><P>
<B>References:</B> Chapter 1, Working draft of <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A><P>
<B>Category:</B> Clarification<P>
Related Issues: CONFORMANCE-POSITION, IF-BODY, ERROR-TERMINOLOGY, EXTRA-SYNTAX,<P>
EXTRA-OPTIONAL-KEYWORD-ARGUMENTS, UNSPECIFIED-DATATYPES,<P>
<A HREF="iss227.htm">MACRO-AS-FUNCTION</A>, UNSOLCITED-MESSAGES, <A HREF="iss156.htm">EXTRA-RETURN-VALUES</A><P>
<B>Edit history:</B> 12-DEC-88, Version 1 by Chapman<P>
20-DEC-88, Version 2 by Chapman<P>
9-JAN-89, Version 3 by Chapman<P>
10-JAN-89, Version 4 by Chapman<P>
2-FEB-89, Version 5 by Chapman<P>
24-FEB-89, Version 6 by Chapman (added RPG's comment)<P>
10-MAR-89, Version 7 by Chapman (added discussion)<P>
<P>
<B>Problem Description:<P>
</B> <P>
What is the definition of a language extension?<P>
What effect does a language extension have on a conforming program? <P>
What obligation does an implementation have to warn the user that an <P>
extension is being used?<P>
<P>
Presumably the only thing that defining it as an extension can mean from<P>
CL's point of view is `initially defining' it as an extension. Whether<P>
an implementation permits redefinition of an extension is between that<P>
implementation and its users and beyond the scope of Common Lisp. For<P>
example, it is common practice to redefine some kinds of system functions<P>
in Genera -- to extend the system in interesting ways, to fix bugs, etc.<P>
<P>
<P>
Proposal (<A HREF="iss154.htm">EXTENSIONS-POSITION:DOCUMENTATION</A>)<P>
<P>
The <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A> document should define a language extension to be<P>
any implementation-supplied tool that isn't explicitly defined<P>
in the <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A>. This includes facilities added to tools defined<P>
in the <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A>.<P>
The <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A> document should levy the following requirement on a <P>
conforming implementation's documentation:<P>
The documentation that accompanies a conforming implementation should clearly<P>
state which parts of the implementation are extensions. <P>
<P>
<P>
If the <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A> says that &quot;the results are unspecified&quot;, and an<P>
implementation specifies the results, this an extension in the<P>
sense that if the correct behavior of a program depends on the results,<P>
only implementations with the same extension will execute the program<P>
correctly.<P>
<P>
In places where the <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A> says that &quot;an implementation may be extended&quot;,<P>
this implies that a conforming, but probably non-portable, program can<P>
be written using the implementation's extension.<P>
<P>
Proposal (EXTENSIONS-POSITION:DISABLE)<P>
<P>
Same as <A HREF="iss154.htm">EXTENSIONS-POSITION:DOCUMENTATION</A> except that<P>
an implementation is required to have a way to disable its extensions, so<P>
that a programmer can be told when he is using a feature that might<P>
affect his program's portability. <P>
<P>
<P>
<B>Rationale:<P>
</B> <P>
The <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A> should contain information about language extensions<P>
since most implementations have extended the language.<P>
<P>
<B>Current Practice:<P>
</B><P>
CLtL allows any extension, provided that it doesn't alter the behavior<P>
of a program that only uses what is specified in CLtL. In particular,<P>
any situation that &quot;is an error&quot; (either explicitly or implicitly) is a<P>
potential area for extension.<P>
<P>
<P>
<B>Adoption Cost:<P>
</B> <P>
Vendors will have to improve their documentation<P>
to list all their extensions. Vendors will have to go through their<P>
implementation and determine what is or isn't an extension.<P>
<P>
<P>
<B>Benefits:<P>
</B> <P>
This definition will <A REL=DEFINITION HREF="../Body/f_provid.htm#provide"><B>provide</B></A> a basis for proper understanding of <P>
the error terminology used in the <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A>. The implementation<P>
documentation requirement will aid the user in producing portable code.<P>
<P>
<B>Conversion Cost:<P>
</B> <P>
None.<P>
<P>
<B>Aesthetics:<P>
</B> <P>
None.<P>
<P>
<B>Discussion:<P>
</B>Masinter says:<P>
It seems to be a constraint on &quot;documentation&quot; rather than &quot;implementation&quot;<P>
if you turn the accidental behavior of (<A REL=DEFINITION HREF="../Body/f_car_c.htm#car"><B>CAR</B></A> T) into a &quot;feature&quot; of your<P>
implementation. We might want to disallow such an extension as &quot;conforming<P>
to the standard&quot;. An implementation which had such an extension might<P>
conform, even if the extension did not conform.<P>
<P>
RPG says:<P>
I favor remaining mute on this topic in the <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A>.<P>
<P>
Moon says:<P>
&quot;I favor <A HREF="iss154.htm">EXTENSIONS-POSITION:DOCUMENTATION</A>.<P>
<P>
I oppose EXTENSIONS-POSITION:DISABLE because it mandates a<P>
particular development environment feature, but Common Lisp<P>
has avoided saying anything about development environments<P>
since that is an area of extreme controversy.<P>
<P>
Gabriel's position of standing mute would be okay with me.&quot;<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>