[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue DEFCONSTANT-NOT-WIRED (V2)
- To: David N Gray <Gray@DSG.csc.ti.com>
- Subject: Re: Issue DEFCONSTANT-NOT-WIRED (V2)
- From: Brad Miller <miller@CS.ROCHESTER.EDU>
- Date: Fri, 28 Oct 88 14:04 EDT
- Cc: CL-Compiler@SAIL.STANFORD.EDU
- In-reply-to: <2802989729-1516801@Kelvin>
- Organization: University of Rochester, Department of Computer Science
- Phone: 716-275-1118
- Postal-address: 610 CS Building, Comp Sci Dept., U. Rochester, Rochester NY 14627
- Reply-to: miller@CS.ROCHESTER.EDU
- Sender: miller@CS.ROCHESTER.EDU
Date: Thu, 27 Oct 88 19:15:29 CDT
From: David N Gray <Gray@DSG.csc.ti.com>
Issue: DEFCONSTANT-NOT-WIRED
References: CLtL pages 68-69
Related issues: Proposals DEFCONSTANT-VALUE:COMPILE-TIME and
COMPILE-FILE-HANDLING-OF-TOP-LEVEL-FORMS:CLARIFY
Does this mean I can do:
(defvar *mumble*)
(defun foo ()
(setq *mumble* :bar)
(proclaim '(constant *mumble*)))
(defun bar ()
(setq *mumble* :foo))
then
(foo)
:bar
(bar)
ERROR...
vs.
(bar)
:foo
(foo)
:bar
(foo)
ERROR...
??? If so, I don't buy it; the compiler shouldn't have to hook setq.
----
Brad Miller U. Rochester Comp Sci Dept.
miller@cs.rochester.edu {...allegra!rochester!miller}