[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Issue Status

This is my status file as of today. Please give your attention to the
???? issues; if you want to send me one general message covering your
opinion or non-opinion on various messages, I will try to sort it out. 


Annotations:
* ready for release (I think)
< already approved, no more action pending.
{ awaiting action from some other committee
% need volunteer to write up
???? A question: Please reply.
~ Tabled until resubmitted, i.e., no immediate action proposed.

!
* Proposal format (Version 12, 23-Oct-87)
 Format for proposals to the cleanup committee.
 Version 12 mailed October 23, 1987
???? Ready for release? 

ADJUST-ARRAY-DISPLACEMENT (Version 3, 5-jun-87)
 (Standardize interaction of adjust-array and displacement)
 Discussion about :displaced-to nil vs. no :displaced-to.
 Need volunteer to revise, clarify :displaced-to ommitted
      same as :displaced-to nil.
 Not ready for release.

% ADJUST-ARRAY-FILL-POINTER-SOURCE (not yet submitted - from ISSUES
file)
 (p 297) "Specify that the fill pointer is ignored for the
 purposes of deciding whether a given element of a new array
 resulting from ADJUST-ARRAY should take its value from the
 old array contents or from the specified :INITIAL-ELEMENT."

ADJUST-ARRAY-NOT-ADJUSTABLE (version 1, 22-apr-87)
 (Extend adjust-array so its OK on non-adjustable arrays.)
 Several comments which need reply
 Not ready for release.
 Notes from boston cl-cleanup meeting have *, but
  the mail traffic seems inconclusive.

APPEND-DOTTED (version 1, 27 Jul 87)
 Sumbitted by KMP.
 Need mod to Current Practice
 Mention (append () t), clarify NCONC?
 Not ready for release.

% APPLY-HOOK-SPECIAL-FORMS (not yet submitted/from ISSUES file) 
 (p 322) At end of second paragraph on *APPLYHOOK*,
 clarify that the apply hook function is not used
 when special forms are evaluated.
 Need volunteer to submit.

* AREF-1D (Version 6/6 JUL 87)
 (Add a new function for accessing arrays with row-major-index)
 Version 5 conditionally passed at X3j13/Jun87 pending new version.
 Version 6 mailed to cl-cleanup 6Jul.
???? Ready for release with endorsement?

~ ASSOC-RASSOC-IF-KEY (Version 1, 22 Apr 87)
 (Extend ASSOC-IF, etc.  to allow :KEY)
 Needs revision of current practice, test case, example.
 (Only Symbolics is known to implement this feature)
 Not ready for release

* COLON-NUMBER (Version 1, 22-oct-87)
  (Is :1 a number, a symbol, or undefined?)
???? Ready for release?

{ COMPILER-WARNING-BREAK (Version 2/7-Apr-87)
 (Does *BREAK-ON-WARNING* affect the compiler?)
 Questions on interaction with condition proposal. 
 Await error proposal

< COMPILER-WARNING-STREAM (Version 6/ 5-Jun-87)
 (Compiler warnings are printed on *ERROR-OUTPUT*)
 Version 6 passed X3J13/Jun87.

% CONSTANT-SIDE-EFFECTS (not yet submitted)
   (it is an error to do destructive operations on constants in code,
   defconstant.)
   Discussed 12/86 - 1/87
   Need volunteer to submit

% DATA-TYPES-HIERARCHY-UNDERSPECIFIED (not yet submitted)
  (Should STREAM, PACKAGE, PATHNAME,  READTABLE, RANDOM-STATE be
  required to be disjoint from other types?)
   From CLOS committee, not yet submitted

* DECLARE-MACROS (version 1, 22-oct-87)
   (Allowing macros to expand into declarations is not worth
    the ambiguity & implementation cost.)
???? Ready for release?

% DECLARATION-SCOPE (not yet submitted)
   (What is the scope of SPECIAL declarations?
   INLINE declarations? where can declarations be placed?)
   Discussed at length, but no formal proposals.

DEFINITION-FUNCTIONS (no formal proposal)
  (Extensions for documentation-type for delete-definition
  for type FUNCTION, VARIABLE, TYPE. )
  Rough draft mailed  9-Oct-87.
  Is all of this mechanism necessary?

DEFMACRO-BODY-LEXICAL-ENVIRONMENT (not yet submitted)
  What is the lexical environment of DEFTYPE, DEFINE-SETF bodies?
  Mail 11-12 Oct 87 on common-lisp
  Pavel may propose something here.

{ DEFSTRUCT-SLOTS-CONSTRAINTS (not yet submitted/issues file)
(p 307) "Allow a call to DEFSTRUCT to have no slot-descriptions.
 Specify that it is an error for two slots in a single DEFSTRUCT to
 have the same name.  If structure A includes structure B, then no
 additional slot of A may have the same name as any slot of B."
   Await object proposal.

{ DEFSTRUCT-DEFAULT-VALUE-EVALUATION (not yet submitted/issues file)
(p 305) "The default value in a defstruct slot is not evaluated
 unless it is needed in the creation of a particular structure
 instance.  If it is never needed, there can be no type-mismatch
 error, even if the type of the slot is specified, and no warning
 should be issued."
  Await object proposal.

* DEFVAR-DOCUMENTATION (Version 1, 30-Jun-87)
   (Documentation string is not evaluated.)
   Submitted, no replies
???? Ready for release with endorsement?

< DEFVAR-INITIALIZATION (Version 4/Jun-87)
 ((DEFVAR var) doesn't initialize)
 Version 4 passed X3J13, Jun87.

< DEFVAR-INIT-TIME (Version 2/29-May-87)
 (DEFVAR initializes when evaluated, not later.)
 Version 2 passed X3J13/Jun87.

% DISASSEMBLE-SIDE-EFFECT (not yet submitted/from ISSUES.TXT)
 "Clarify that if DISASSEMBLE is given a symbol whose function
 definition is interpreted, that definition is indeed compiled
 and then disassembled, but the resulting compiled definition
 does not replace the interpreted one as the symbol's function
 definition."
 Need volunteer to submit.

DO-SYMBOLS-DUPLICATES (Version 2, 29-May-87)
 (can DO-SYMBOLS see the same symbol twice?)
 Debate: extend so that both options are available?
 Needs more information on implementation and
   performance cost.
 Masinter will rewrite, flush :ALLOWED option,
  rewrite :ADD-KEYWORDS to make default for
  :ALLOW-DUPLICATES as NIL., conversion cost => nil.
 Not ready for release.

~ EVAL-DEFEATS-LINKER (Version 1, 12 Jun-87)
 ("selective linking" means GC non-used symbols; 
 proposal to change #., #, and part of FUNCTION-TYPE
 Wait on FUNCTION-TYPE, deal with #., #, changes 
 independently.

EXPORT-COORDINATION (no formal proposal)
  Coordinate EXPORT and DEFxxx by adding new form.
  Is this a good idea to allow?
  Not yet formally submitted.
  Looking for proposal to make package manipulation lexical.

{ FILE-WRITE-DATE-IF-NOT-EXISTS (from Weinreb, no fromal proposal)
 (What does FILE-WRITE-DATE do if no such file?)
 "there should not be a formal proposal for fixing the file-write-date 
 ambiguity until we are at the point where we can make proposals
 that discuss signalling named conditions. "
  Awaiting error proposal.

% FILE-LENGTH-PATHNAME (not submitted, from ISSUES.TXT)
(P 425) "Generalize FILE-LENGTH to accept any filename, not just an open
file-stream.  Let it take a keyword argument :ELEMENT-TYPE, defaulting
to STRING-CHAR for non-stream arguments and to the element-type of the
stream for a stream argument."
  Need volunteer to write up.

< FLET-IMPLICIT-BLOCK (Version 6/ 5-Jun-87)
 (do FLETs have implicit named blocks around them?)
 Version 6 passed X3J13/Jun87.

< FORMAT-ATSIGN-COLON (Version 4/5-jun-87)
 ( @: == :@ in format)
 Version 4 passed X3J13/Jun87.

* FORMAT-COMMA-INTERVAL (Version 1/10 June 87)
 (Allow another argument to ~D etc to paramerize digits between commas)
???? Ready for release with endorsement?

% FORMAT-NEGATIVE-PARAMETERS (mail 19 May, no formal proposal)
  "format parameters are assumed to be non-negative integers except
    as specifically stated"
   Need volunteer to write up.

< FORMAT-OP-C (Version 5/ 11-Jun-87)
 (What does ~C do?)
 Version 5 passed X3J13/Jun87.

* FUNCTION-TYPE (Version 6, 23-Oct-87)
 (Change definition of FUNCTIONP, function type ...)
 Draft released 16-Jun-87.
 Discussed at X3J13, new proposal due.
??? STRICT-REDEFINITION ready for release?

% FUNCTION-TYPE-REST-LIST-ELEMENT (not yet submitted)
 (allow &rest <type> in function types to refer to element
 type rather than list)
 Disscussed at length in the past.
 Need volunteer to submit.

% FUNCTION-SPECS (not yet submitted)
   (add "function specs" for defun, trace
  etc) Mail from Moon 16-Jun. 
  cf SETF-FUNCTION-VS-MACRO.

~ GC-MESSAGES (version 1)
 (Control over unsolicited GC messages in typescript)
 merge with other controls for unsolicited messages?
 Not ready for release.
 Pitman volunteered to revise.

* GET-SETF-METHOD-ENVIRONMENT (Version 5, 13-Jun-87)
 (Environment argument for GET-SETF-METHOD)
 Version 4 conditionally passed X3J13/Jun87.
 Version 5 mailed 13-Jul-87 13:18:47 
???? Ready for release?

{ IF-BODY (Version 7, 16-Jun-87)
 (extend IF to implicit progn if more than one ELSE form?)
 Draft released 16-Jun-87.
 Discussed at X3J13/Jun 87.
 Postpone pending resolution of policy on extensions

{ IGNORE-ERRORS (Version 4, 29-May-87)
 (Introduce error catcher) 
 Pitman will release as report from cleanup + error committee.
 Awaiting error proposal

< IMPORT-SETF-SYMBOL-PACKAGE (Version 5, 11-Jun-87)
 (Does IMPORT affect home package?)
 Version 5 passed X3J13/Jun87.

* KEYWORD-ARGUMENT-NAME-PACKAGE (Version 7, 23-Oct-87)
 ( &KEY arguments not in keyword package?)
 Version 6 conditionally passed X3J13/Jun87.
???? Ready for release?

% LISP-SYMBOL-REDEFINITION  (no formal proposal yet)
  Is it legal to redefine symbols in the LISP package?
  Mail 14-Aug-87

& LOAD-TIME-EVAL (Version 2, 17-JUL-87)
 (New function/macro/special form for evaluation when 
 compiled file is loaded?)
 No discussion after Version 2.
???? ready for release?

% MACRO-FUNCTION-ENVIRONMENT 
 (Add environment argument to MACRO-FUNCTION?)
 From ENVIRONMENT-ARGUMENTS
 Formal proposal not yet submitted.
 re-extract from environment-arguments?
 CLOS notes say they need this?

* OPEN-KEYWORDS-EXISTS (Version 1, 17-Jul-87)
  No discussion.
???? Ready for release ?

* PATHNAME-STREAM (Version 5, 23-Oct-87)
 (PATHNAME only works on file streams)
 Version 2 conditionally passed X3J13/Jun 87
 *must* the pathname be the one supplied to open? 

~ PATHNAME-SUBDIRECTORY-LIST (Version 1, 18-Jun-87)
  How to deal with subdirectory structures in pathname functions?
  Proposal for :SUBDIRECTORY rejected; make :DIRECTORY a structure?
  Unlikely to be portable.

* PATHNAME-SYMBOL (Version 3, 23-OCT-87)
 (Do symbols automaticly coerce to pathnames?)
???? Ready for release?

% PATHNAME-UNSPECIFIC-COMPONENT (not yet submitted)
  Mail Aug 87 discussion
  How to deal with logical devices, :unspecific components,
    etc in pathname functions
  RWK@YUKON.SCRC.Symbolics.COM may submit proposal.

~ PEEK-CHAR-READ-CHAR-ECHO (Version 1, 3 March 87)
 (interaction between PEEK-CHAR, READ-CHAR and streams made by
  MAKE-ECHO-STREAM)
 "Fixing echo streams is fine, but I don't think that
    it is appropriate for the standard to specify how terminal
interaction
    must or even ought to work."

< PRINC-CHARACTER (Version 3)
 (PRINC behavior on character objections)
 Version 3 passed X3J13/Jun87.

PROCLAIM-LEXICAL  (Version 1)
 (add LEXICAL proclaimation, default binding type for
  undeclared free variables)
 Not ready for release.
 This got sidetracked. Lets try to hash this one out.

~ PROMPT-FOR (Version 1)
 (add new function which prompts)
 Tabled until re-submitted.

* PUSH-EVALUATION-ORDER (Version 2, 23-Oct-87)
 (What order does (PUSH (A) (CAR (B))) evaluate (A) and (B)?)
 Also INCF, PUSHNEW, etc.
??? Ready for release?

REMF-DESTRUCTION-UNSPECIFIED (Version 1)
 (How does REMF affect its arguments?)
 discussion Feb 87.
  Lets get this one moving...

* REQUIRE-PATHNAME-DEFAULTS (Version 1, 15-Oct-87)
  (where does REQUIRE look for files?)
  Does it solve our problems?
??? Ready for release?

SETF-METHOD-FOR-SYMBOL (Version 2, 23-oct-87)
  (Change recommendation for (get-setf-method symbol)?)
  "Maybe we should fix the definition for setf of ldb rather than
  the values returned for symbol?"
  Not ready for release.

* SETF-FUNCTION-VS-MACRO (Version 1, 15-Oct-87)
  (Allow (DEFUN (SETF FOO) ..))
  Discussed at length on CLOS
???? Ready for release with Masinter's edits?

* SEQUENCE-FUNCTIONS-EXCLUDE-ARRAYS (Version 2, 28-Apr-87)
 (FIND, SUBSTITUTE etc work on multi-dimensional arrays?)
 No discussion since May-87
???? Release GENERALIZE option?

* SHADOW-ALREADY-PRESENT (Version 2, 27 Aug 87)
  Revised according to discussion
???? Ready for release?

{ SHARPSIGN-BACKSLASH-BITS
 (What does C-META-H-X mean?)
 Forwarded to character committee.

~ SHARPSIGN-PLUS-MINUS-NUMBER
 (Is #+68000, #-3600 allowed?)
 Mild disagreement: it is an error?
 Table until resubmitted

SHARPSIGN-PLUS-MINUS-PACKAGE (version 2, 9-Mar-87)
 (What package are *features* in?)
 Mild support for :KEYWORD
 Register *features*?
???? Report out with only :KEYWORD proposal?

% SPECIAL-FORM-SHADOW (no formal proposal)
 (Is it OK to shadow a special form with FLET, LABELS, MACROLET?)
 In discussion, no formal proposal submitted.

% STANDARD-INPUT-INITIAL-BINDING (from ISSUES.TXT file)
(P 328) "Remove the requirement that *STANDARD-INPUT*, etc., must be
initially bound to synonym streams to *TERMINAL-IO*; demote this to the
level of an implementation suggestion.  This is to allow flexibility of
implementation, for example to allow UNIX redirection to win."
  Need volunteer to submit

% STREAM-CLASS-ACCESS (No formal proposal)
(Originally FOLLOW-SYNONYM-STREAM 19-DEC-86)
  Define stream accessors as if synonym-stream two-way-stream etc were
  CLOS classes?

{ STRUCTURE-DEFINITION-ACCESS (No formal proposal)
 (access to slot accessors for DEFSTRUCT etc.)
 Await CLOS

% SUBSEQ-OUT-OF-BOUNDS (from ISSUES file, no formal proposal)
(p 246) "Specify that it is an error for the SUBSEQ indices or any
:START or :END argument have a negative index or point past the end of
the sequence in question.  (With respect to whether signalling is
required, this error will be treated the same as array out-of-bounds.)"
 Need volunteer to write up

% TAILP-NIL (no formal proposal yet)
 (Operation of TAILP given NIL)
  Needs writeup in current format.

TRACE-FUNCTION-ONLY (Version 1, 21-Oct-87)
  (Allow trace for SETF functions, macros, etc.)
  Environment extension?

UNWIND-PROTECT-CLEANUP-NON-LOCAL-EXIT (Version 2, 24-Oct-87)
 (GO out of UNWIND-PROTECT clauses.)
 Need decision among 3 proposals.