> > Having it in the core, in C[++], would be that much more efficient, > > and that much less of a hack. Maybe the tradeoff is that it > > wouldn't work. :-) > > Everyone's making these assumptions, WHY WON'T ANYONE LOOK AT > CLASS::OBJECT?! It might not work, Schwern. And even if it did, it might be really slow. Somebody should write an implementation first, and then tackle efficiency. Something like sub sub { my ($self, $method_name, $method ) = @_; *{ref($self).'::'.$method_name} = $method; } for adding object methods would be a good start. I think I'll call it Class::Object. Dan
- Re: Per-object inheritance in core a red herring? Dan Sugalski
- Re: Per-object inheritance in core a red herring? Nathan Torkington
- 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? schwern
- Re: Per-object inheritance in core a red herring? Michael Fowler
- Re: Per-object inheritance in core a red herring? John Porter
- Re: Per-object inheritance in core a red herring? Michael G Schwern
- Re: Per-object inheritance in core a red herring? Dan Brian
- 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