[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
time of evaluation of defstruct, deftype, etc.
- To: Scott E. Fahlman <Fahlman@C.CS.CMU.EDU>
- Subject: time of evaluation of defstruct, deftype, etc.
- From: David A. Moon <Moon@SCRC-STONY-BROOK.ARPA>
- Date: Wed, 15 Jan 86 21:50 EST
- Cc: common-lisp@SU-AI.ARPA
- In-reply-to: <FAHLMAN.12175557655.BABYL@C.CS.CMU.EDU>
Date: Wed, 15 Jan 1986 20:35 EST
From: "Scott E. Fahlman" <Fahlman@C.CS.CMU.EDU>
This problem cannot be solved with multiple address spaces, unless you have a
very complicated mechanism for sharing objects between address spaces,
I don't understand this. What has to be shared in a complicated way?
Copy-on-write is fine for getting things to the compiler, but what if you want to
get something back?
I don't want to get into a long discussion of this.
Stepping back a level, the main issue for the Common Lisp community is do
we want to say that this is an issue which each implementation should solve
for itself, in order to have a compiler that can be considered "high quality",
or is this something that should be made a standard part of the language,
with a portable interface? Obviously one alternative is "better" for the
users and the other alternative is less work for the language standardization
As I said in my answer to Weinreb, the way you want to go about solving
this problem depends a lot on the kind of system you're running in.
So your position is that this should not be made a standard part of the language.