[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: BUG-LISP at MIT-AI
- Subject: DEFVST
- From: Edward Barton <EB at MIT-AI>
- Date: Sat, 15 Mar 80 04:37:00 GMT
- Original-date: 14 March 1980 23:37-EST
What is the proper way to make DEFVST constructions intelligible
to the compiler but unavailable at runtime?
(defvst barf a b c))
(defun foo () (cons-a-barf a 1 b 2 c 3))
seems reasonable, but this causes the result of (FOO) to produce
a hunk whose struct-typep is nil and which contains "UNBOUND"
for at least one component. (where FOO is loaded compiled)