On Tue, Jul 10, 2001 at 02:08:58AM -0500, David L. Nicol wrote: > Uh, C++ virtual methods can be overloaded on a per-object basis, not > just a per-class basis, since the object drags around its virtual jump > table with it wherever it goes, so the jump can get compiled into > "jump to the address that is <offset> bytes away from the start of > the object that is doing the method" which is pretty light, unless > you've got dozens of virtual methods. And what's the linguistic hook that allows C++ object-based inheritance? And where's the guarantee that vtbls are per-object and not per-class? Z.
- 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? David L. Nicol
- 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? David L. Nicol
- Re: Per-object inheritance in core a red herring? Adam Turoff
- Re: Per-object inheritance in core a red herring? David L. Nicol
- Re: Per-object inheritance in core a red herring? David L. Nicol
- 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
- Re: Per-object inheritance in core a red herring? David L. Nicol
- Re: Per-object inheritance in core a red herring? Dan Sugalski