[EMAIL PROTECTED] wrote: > "Any sufficiently encapsulated hack is no longer a hack." Who said that? I think it's wrong. Any sufficiently encapsulated hack is no longer a *naked* hack. So what. > You shouldn't be relying on an object's reference. ref $obj eq > 'Some::Class' wrecks subclassing, ref($a) eq ref($b). > What's the trade-off here? It works, its efficient, the hacks are > well encapsulated. 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. :-) -- John Porter
- Per-object inheritance in core a red herring? Michael G Schwern
- Re: Per-object inheritance in core a red herring? John Porter
- 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 herrin... 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 herrin... David L. Nicol
- Re: Per-object inheritance in core a red herring? schwern
- Re: Per-object inheritance in core a red herring? Uri Guttman