At 02:10 PM 7/10/2001 -0400, Mark J. Reed wrote:
>Not quite authoritative, I'm afraid. :) I'm looking at the new edition
>of the Stroustroup book, and the very existence of vtables is an
>implementation detail not guaranteed by the language spec (now that
>there actually is a language spec for C++). Further, in the example
>which mentions vetables, each object has a pointer to a vtable which is shared
>by the entire class.
>
>Which is not to say that it couldn't be moted so for Perl . . .
I was moting it for perl. Alas, reading comprehension doesn't seem to be a
requirement for the internals design chair and I missed the rather
important language distinction in the original message... :(
>On Tue, Jul 10, 2001 at 01:44:35PM -0400, Dan Sugalski wrote:
> > At 11:01 AM 7/10/2001 -0400, Adam Turoff wrote:
> > >And where's the guarantee that vtbls are per-object and not per-class?
> >
> > VTABLES ARE PER OBJECT.
> >
> > So mote it be. :)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
