Chaim Frenkel <[EMAIL PROTECTED]> writes: > >And why carry around IV/NV and ptr? Make it into a union, to allow room. _my_ original "ramblings" posting did. I kept the triple to pad the thing to 8 words. Partly as devil's advocate against the "squeeze it all into one word" camp ;-) Essentially what I am proposing is removing the sv_any indirection for the simple scalar cases this reduces housekeeping, indirections and keeps actual data near "SV/PMC" for cache reasons. > >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. All true - but we can minimize the malloc-ing that such conversions entail if we have a "reasonable" amount of (multi-purpose) storage in the root. -- Nick Ing-Simmons
- Re: RFC 35 / Re: perl6-internals-gc sub... John Tobey
- 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: RFC 35 / Re: perl6-internals-gc sub... 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