[LISPWORKS][Common Lisp HyperSpec (TM)] [Previous][Up][Next]


Date: Thu, 09 Jan 92 13:34:34 EST

From: kab@cambridge.apple.com (Kim Barrett)

To: kmp@symbolics.com

Subject: jun90-trivial-issues


Status: Passed Jun 90

Here is a list of (what I consider to be) fairly trivial issues

from the list I circulated some time ago, along with a one-line

fix for the problem. I'm hoping they are noncontroversial enough

so that we can just have one vote to approve the whole bunch. If

you *really* want to see a full cleanup issue and have a separate

vote on any of these, let me know....

The numbering follows my original list.


behavior "when *PRINT-ESCAPE* is T". Change "T" to "true" but

don't change the behavior.

(4) Rule (2) in issue PUSH-EVALUATION-ORDER specifies some

behavior for the macro GETF, but GETF is actually a function.

Since the order of evaluation of its arguments is already

well-specified, remove GETF from the list of affected macros

in this issue.

(5) Issue PATHNAME-COMPONENT-CASE specifies some behavior for

a function named TRANSLATE-WILD-PATHNAME, which is not fully

defined anywhere else. Change the reference to



STRUCTURE-OBJECT were not formally defined as class names in

CLOS chapters 1 and 2, although they were documented in the

Aug 89 draft of the standard. Formally add these classes to

the language as documented in the draft.

(11) Clarify that symbols that are defined as LOOP macro

keywords are not exported from the COMMON-LISP package unless

they have some other definition in the language. The equality

test used by LOOP to match keywords is a STRING= test on the


(14) Issue CONDITION-RESTARTS states that restarts have dynamic

extent, but doesn't say what the lifetime of that extent is.

Clarify that it is the same as the lifetime of the binding of

the restart.

(24) The character committee proposals stated that BASE-STRING

and SIMPLE-BASE-STRING are valid as type specifiers that

abbreviate. Clarify that the list forms of these type specifiers

have the same syntax as the list form of the STRING type


(25) Clarify that, when there is a dribble file already open,

the behavior when DRIBBLE is called again to open another dribble

file is unspecified. (Some possible behaviors are: close

the first file; dribble to both files; leave the first file open

but dribble only to the second until it is closed; or to ignore

the new dribble request entirely.)

(27) Clarify that SETF places THE and APPLY support multiple

store variables. (See issue SETF-MULTIPLE-STORE-VARIABLES.)

[Starting Points][Contents][Index][Symbols][Glossary][Issues]
Copyright 1996-2005, LispWorks Ltd. All rights reserved.