At 06:07 PM 6/28/2001 -0700, Brent Dax wrote:
>I'd think that @ISA would be copied to .ISA on object instantiation, and
>after that the two wouldn't have anything to do with each other. We could
>set up one of those cool copy-on-write locks everyone's been talking about
>to save memory too.
Yep, we could do that. Whether it's worth it or not depends on whether
objects generally have other properties besides .ISA. If not then it's a
bit of a waste of space since we'd be instantiating an entry in the
property hash where we wouldn't otherwise have one.
>Or we could have it default to @ISA if .ISA doesn't exist, which is
>basically what Bart's saying, so I guess I agree with him, maybe. (Although
>I do think that when .ISA is created, it should get @ISA, whenever that
>happens to be.)
At the language level, objects should get their class' @ISA in addition to
anything dumped in .ISA. At the implementation level, I'd rather not since
that'd require chewing up more memory, but if it ends up being worthwhile
then, well, we'll do it.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
