At 11:24 AM 7/11/2001 -0500, David L. Nicol wrote: >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 > >What? Up until now it's been vtable-pointers are per-object. They are. Who says they need to share what's pointed to? That's a space and creation time optimization. :) Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- Re: Per-object inheritance in core a red herring? schwern
- Re: Per-object inheritance in core a red herring? Dan Sugalski
- Re: Per-object inheritance in core a red herring? Dan Sugalski
- Re: Per-object inheritance in core a red herring? schwern
- Re: Per-object inheritance in core a red herring? Uri Guttman
- Re: Per-object inheritance in core a red herring? Adam Turoff
- Re: Per-object inheritance in core a red herring? Dan Sugalski
- Re: Per-object inheritance in core a red herring? Dan Sugalski
- Re: Per-object inheritance in core a red herring? Mark J. Reed
- Re: Per-object inheritance in core a red herring? Dan Sugalski