Chaim Frenkel wrote: > The string/number duality should be handled by the vtbl. So a string that > is never accessed as a number, doesn't waste the space. And numbers that > are rarely accessed as a string save some room. And as needed the vtbl can > be promoted to a duality version that maintains both. I agree with that. I believe we sould push as much as we can into the vtbl. This will make reimplmentation of Perl guts in say, Java, much easier. :) -- Bradley M. Kuhn - http://www.ebb.org/bkuhn
- Re: RFC 35 / Re: perl6-internals-gc sub... Ken Fox
- Re: RFC 35 / Re: perl6-internals-gc sub... Dan Sugalski
- Re: RFC 35 / Re: perl6-internals-gc sub... John Tobey
- Multi-object locks (was Re: RFC 35 / Re... Chaim Frenkel
- Re: Multi-object locks (was Re: RFC 35 ... Dan Sugalski
- Re: Multi-object locks (was Re: RFC 35 ... Chaim Frenkel
- Re: Multi-object locks (was Re: RFC 35 ... Larry Wall
- Re: Multi-object locks (was Re: RFC 35 ... Chaim Frenkel
- Re: RFC 35 / Re: perl6-internals-gc sub... Ken Fox
- Re: RFC 35 / Re: perl6-internals-gc sub... Nick Ing-Simmons
- Re: perl6-internals-gc sublist Bradley M. Kuhn
- Re: perl6-internals-gc sublist Dan Sugalski
- Re: perl6-internals-gc sublist John Tobey
- Re: perl6-internals-gc sublist Dan Sugalski
- Re: perl6-internals-gc sublist John Tobey
- Re: perl6-internals-gc sublist Dan Sugalski
- Re: perl6-internals-gc sublist John Tobey
- Re: perl6-internals-gc sublist Nathan Torkington