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

Issue Status (reply solicited)

This is a revised version of the status file I sent out 22-Sep-87. I
have now gone through the mail I have on each issue, and attempted to
reflect what I think the current status is. As usual, if you want a copy
of the issue to refresh your memory or your mail archive, let me know.
(Someday I will be able to store these on a directory you have access

In some cases, I've indicated a question ???? on whether an item is
ready to release. I'd like everyone to reply, either with an accept,
don't care, or object on each releasable item. 

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

In particular, if it says "???? Ready for release with endorsement", I
propose to edit the last submitted version of the proposal as sent to
CL-CLEANUP to include the statement that the cleanup committee endorses
the proposal, and send it on to X3J13. A simple one-line "please don't
release yet" reply will suffice. 

* Proposal format (Version 12)
 Format for proposals to the cleanup committee.
 Version 11 released 11-Jun-87.
???? Release version 12 with "Related issues" field? 

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[lmm?] 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 2/15-Jun-87)
 (Extend ASSOC-IF, etc.  to allow :KEY)
 Needs revision of current practice, test case, example.
 (Only Symbolics is known to implement this feature)
 The summary says Version 2, but I only have version 1 on file.
 Not ready for release
???? Does anyone else have a version 2? Or was this wishful thinking?

{ COMPILER-WARNING-BREAK (Version 2/7-Apr-87)
 (Does *BREAK-ON-WARNING* affect the compiler?)
 Questions on interaction with condition proposal. 
 Postponed pending 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,
   Discussed 12/86 - 1/87
   Need volunteer to submit

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 (not yet submitted)
  (Extensions for documentation-type for delete-definition
  Rough draft mailed  9-Oct-87.
  Very preliminary.

{ 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.

   (Documentation string is not evaluated.)
   Submitted, no replies
???? Ready for release with endorsement?

 ((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.

 "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
 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)
   Postpone pending FUNCTION-TYPE resolution & 
	handle remainders.

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.

(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 5/ 16-Jun-87)
 (Change definition of FUNCTIONP, function type ...)
 Draft released 16-Jun-87.
 Discussed at X3J13, new proposal due.

 (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. 

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 
???? release with endorsement

{ 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.

 ( &KEY arguments not in keyword package?)
 Version 6 conditionally passed X3J13/Jun87.
 Rewrite using CLOS terminology ("named argument")
 instead of  "keyword argument".
 Need volunteer to rewrite

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 with endorsement ?

 (Add environment argument to MACRO-FUNCTION?)
 Formal proposal not yet submitted.
 re-extract from environment-arguments?
???? drop this issue ?

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

 (PATHNAME only works on file streams)
 Version 2 conditionally passed X3J13/Jun 87
???? Ready for release ?

  How to deal with subdirectory structures in pathname functions?
  Proposal for :SUBDIRECTORY rejected; make :DIRECTORY a structure?
  Needs revision

 (Do symbols automaticly coerce to pathnames?)
 Not ready for release.
 Needs to be revised, extend language, clarify
   which functions are affected, etc.

  Mail Aug 87 discussion
  How to deal with logical devices, :unspecific components,
    etc in pathname functions

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

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

 (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 (not yet submitted)
 (What order does (PUSH (A) (CAR (B))) evaluate (A) and (B)?)
 Also INCF, PUSHNEW, etc.
 (Mail 20 May 87)

 (How does REMF affect its arguments?)
 Found some discussion dated Feb 87.
???? Pitman will revise & resubmit. ?

SETF-METHOD-FOR-SYMBOL (Version 1, 21-Sep-87)
  In discussion.
  "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 (not yet submitted)
  Proposal in circulation on CLOS discussion for allowing
  (DEFUN (SETF FOO) (new-value ... arguments) ...)
  "Fixing our problems with setf"

 (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?

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

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

 (What package are *features* in?)
 Mild support for :KEYWORD
???? 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.

(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)

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.

 (GO out of UNWIND-PROTECT clauses.)
 Not ready for release.
 Gabriel will revise & resubmit?