1
0
Fork 0
cl-sites/HyperSpec-7-0/HyperSpec/Issues/iss199_w.htm

97 lines
6.9 KiB
HTML
Raw Permalink Normal View History

2024-04-01 10:24:07 +02:00
<!-- 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 JUN90-TRIVIAL-ISSUES 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/iss198_w.htm">
<LINK REL=UP HREF="../Issues/iss199_m.htm">
<LINK REL=NEXT HREF="../Issues/iss208_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/iss198_w.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Previous]" SRC="../Graphics/Prev.gif" ALIGN=Bottom></A><A REL=UP HREF="../Issues/iss199_m.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Up]" SRC="../Graphics/Up.gif" ALIGN=Bottom></A><A REL=NEXT HREF="../Issues/iss208_w.htm"><IMG WIDTH=40 HEIGHT=40 ALT="[Next]" SRC="../Graphics/Next.gif" ALIGN=Bottom></A></H1>
<HR>
<H2>Issue JUN90-TRIVIAL-ISSUES Writeup</H2>
<PRE>Date: Thu, 09 Jan 92 13:34:34 EST<P>
From: kab@cambridge.apple.com (Kim Barrett)<P>
To: kmp@symbolics.com<P>
Subject: <A HREF="iss199_m.htm">jun90-trivial-issues</A><P>
<P>
<B>Issue:</B> <A HREF="iss199_m.htm">JUN90-TRIVIAL-ISSUES</A><P>
<B>Status:</B> Passed Jun 90<P>
<P>
<P>
Here is a list of (what I consider to be) fairly trivial issues<P>
from the list I circulated some time ago, along with a one-line<P>
fix for the problem. I'm hoping they are noncontroversial enough<P>
so that we can just have one vote to approve the whole bunch. If<P>
you *really* want to see a full cleanup issue and have a separate<P>
vote on any of these, let me know....<P>
<P>
The numbering follows my original list.<P>
<P>
(3) Issue <A HREF="iss273.htm">PRINT-CASE-PRINT-ESCAPE-INTERACTION</A> specifies some<P>
behavior &quot;when <A REL=DEFINITION HREF="../Body/v_pr_esc.htm#STprint-escapeST"><B>*PRINT-ESCAPE*</B></A> is T&quot;. Change &quot;T&quot; to &quot;true&quot; but<P>
don't change the behavior.<P>
<P>
(4) Rule (2) in issue <A HREF="iss279_m.htm">PUSH-EVALUATION-ORDER</A> specifies some<P>
behavior for the macro <A REL=DEFINITION HREF="../Body/f_getf.htm#getf"><B>GETF</B></A>, but <A REL=DEFINITION HREF="../Body/f_getf.htm#getf"><B>GETF</B></A> is actually a function.<P>
Since the order of evaluation of its arguments is already <P>
well-specified, remove <A REL=DEFINITION HREF="../Body/f_getf.htm#getf"><B>GETF</B></A> from the list of affected macros<P>
in this issue.<P>
<P>
(5) Issue <A HREF="iss256.htm">PATHNAME-COMPONENT-CASE</A> specifies some behavior for<P>
a function named TRANSLATE-WILD-PATHNAME, which is not fully<P>
defined anywhere else. Change the reference to <P>
&quot;TRANSLATE-WILD-PATHNAME&quot; to &quot;TRANSLATE-PATHNAME&quot;.<P>
<P>
(9) The symbols <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>CLASS</B></A>, <A REL=DEFINITION HREF="../Body/t_generi.htm#generic-function"><B>GENERIC-FUNCTION</B></A>, <A REL=DEFINITION HREF="../Body/t_method.htm#method"><B>METHOD</B></A>, and<P>
<A REL=DEFINITION HREF="../Body/t_stu_ob.htm#structure-object"><B>STRUCTURE-OBJECT</B></A> were not formally defined as <A REL=DEFINITION HREF="../Body/t_class.htm#class"><B>class</B></A> names in<P>
CLOS chapters 1 and 2, although they were documented in the<P>
Aug 89 draft of the <A REL=DEFINITION HREF="../Body/07_ffb.htm#standard"><B>standard</B></A>. Formally add these classes to<P>
the language as documented in the draft.<P>
<P>
(11) Clarify that symbols that are defined as <A REL=DEFINITION HREF="../Body/m_loop.htm#loop"><B>LOOP</B></A> macro<P>
keywords are not exported from the COMMON-LISP package unless<P>
they have some other definition in the language. The equality<P>
test used by <A REL=DEFINITION HREF="../Body/m_loop.htm#loop"><B>LOOP</B></A> to match keywords is a <A REL=DEFINITION HREF="../Body/f_stgeq_.htm#stringEQ"><B>STRING=</B></A> test on the <P>
SYMBOL-NAMEs.<P>
<P>
(14) Issue <A HREF="iss075_m.htm">CONDITION-RESTARTS</A> states that restarts have dynamic<P>
extent, but doesn't say what the lifetime of that extent is.<P>
Clarify that it is the same as the lifetime of the binding of<P>
the restart.<P>
<P>
(24) The character committee proposals stated that <A REL=DEFINITION HREF="../Body/t_base_s.htm#base-string"><B>BASE-STRING</B></A><P>
and <A REL=DEFINITION HREF="../Body/t_smp_ba.htm#simple-base-string"><B>SIMPLE-BASE-STRING</B></A> are valid as type specifiers that<P>
abbreviate. Clarify that the list forms of these type specifiers<P>
have the same syntax as the list form of the <A REL=DEFINITION HREF="../Body/a_string.htm#string"><B>STRING</B></A> type<P>
specifier.<P>
<P>
(25) Clarify that, when there is a <A REL=DEFINITION HREF="../Body/f_dribbl.htm#dribble"><B>dribble</B></A> file already open,<P>
the behavior when <A REL=DEFINITION HREF="../Body/f_dribbl.htm#dribble"><B>DRIBBLE</B></A> is called again to open another <A REL=DEFINITION HREF="../Body/f_dribbl.htm#dribble"><B>dribble</B></A><P>
file is unspecified. (Some possible behaviors are: close<P>
the first file; <A REL=DEFINITION HREF="../Body/f_dribbl.htm#dribble"><B>dribble</B></A> to both files; leave the first file open<P>
but <A REL=DEFINITION HREF="../Body/f_dribbl.htm#dribble"><B>dribble</B></A> only to the second until it is closed; or to ignore<P>
the new <A REL=DEFINITION HREF="../Body/f_dribbl.htm#dribble"><B>dribble</B></A> request entirely.)<P>
<P>
(27) Clarify that <A REL=DEFINITION HREF="../Body/a_setf.htm#setf"><B>SETF</B></A> places <A REL=DEFINITION HREF="../Body/s_the.htm#the"><B>THE</B></A> and <A REL=DEFINITION HREF="../Body/f_apply.htm#apply"><B>APPLY</B></A> support multiple<P>
store variables. (See issue <A HREF="iss309.htm">SETF-MULTIPLE-STORE-VARIABLES</A>.)<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>