[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue: STANDARD-VALUE (Version 1)
- To: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Subject: Re: Issue: STANDARD-VALUE (Version 1)
- From: masinter.pa@Xerox.COM
- Date: 21 Oct 88 13:48 PDT
- Cc: CL-Cleanup@SAIL.Stanford.EDU
- In-reply-to: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>'s message of Fri, 21 Oct 88 16:38 EDT
Envos Medley does this only slightly differently: there's a list
IL:*PER-EXEC-VARIABLES* instead of *STAHDARD-VALUES*. If you really add a
new variable that really has to be rebound when a new debugger or EXEC is
invoked, you can push something onto it.
The initial value is ((*PACKAGE* (COND ((PACKAGEP *PACKAGE*) *PACKAGE*) (T
(PROMPTPRINT "Invalid package, reset to LISP") (SETQ *PACKAGE*
(FIND-PACKAGE LISP))))) (* *) (** **) (*** ***) (+ +) (++ ++) (+++ +++) (-
-) (/ /) (// //) (/// ///) (HELPFLAG T) (*EVALHOOK* NIL) (*APPLYHOOK* NIL)
(*ERROR-OUTPUT* *TERMINAL-IO*) (*READTABLE* *READTABLE*) (*EVAL-FUNCTION*
*EVAL-FUNCTION*) (*EXEC-PROMPT* *EXEC-PROMPT*) (*DEBUGGER-PROMPT*
*DEBUGGER-PROMPT*))
I don't think this will fly, because it seems to be too dependent on one
particular style of debugger.