[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cute PCL in KCl
- To: Gregor.pa@Xerox.COM
- Subject: Re: Cute PCL in KCl
- From: eliot@winnie.Princeton.EDU.Princeton.EDU (eliot handelman)
- Date: Fri, 9 Dec 88 15:55:39 est
- Cc: commonloops.PA@Xerox.COM
- Redistributed: commonloops.PA
>Date: Thu, 8 Dec 88 17:50 PST
>From: Gregor.pa@Xerox.COM
>
>>Date: Thu, 8 Dec 88 19:34:17 est
>>From: eliot@winnie.Princeton.EDU (eliot handelman)
>>
>>One other thing: is there some way to prevent PCl from compiling constructors,
>>must they be compiled at all?
>
>I don't understand your problem here? When are constructors being
>compiled when you don't want them to be?
>
>Constructors should only be compiled when the file containing the
>defconstructor form is compiled. Constructors should not be compiled
>when the file is loaded, when constructors are called, or class or
>method definitions change.
That seems reasonable. So what's going on here?
> *features*
(:PORTABLE-COMMONLOOPS :PCL COMPILER::BUGGY-CC VAX UNIX BSD COMMON KCL
:TURBO-CLOSURE)
> (defclass zit () (volume))
NIL
> (defconstructor make-zit zit (v) :volume v)
NIL
>
(setq a (make-zit 24))
End of Pass 1.
End of Pass 2.
OPTIMIZE levels: Safety=2, Space=3, Speed=3
#<ZIT 14064420>
;; further calls to make-zit don't call the compiler
> (setq b (make-zit 1200))
#<ZIT 15640260>
-Eliot