Lightning flashed, thunder crashed and "Jeremy Howard" <[EMAIL PROTECTED]> whispered: | > > No, neither proposal makes sense. Arrays can be stored compactly and | > | > $a[1_000_000_000] = 'oh, really?' # :-) | > | my int @a: sparse; | $a[1_000_000_000] = 'Yes, really!' # :P | | OK, so I cheated... I haven't submitted my RFC for a 'sparse' attribute yet. | My point is that arrays *can* be stored compactly, not that they always | *are*. Another type of array storage is that required for lazily generated Isn't this just as true, maybe even moreso for hashes? How much storage is taken up by $a{1_000_000_000} = "Sparse, without any special code!"; -spp
- Re: RFC 84 (v1) Replace => (stringif... Russ Allbery
- Re: RFC 84 (v1) Replace => (stringif... Uri Guttman
- Re: RFC 84 (v1) Replace => (stringifying... Dan Sugalski
- Re: RFC 84 (v1) Replace => (stringifying... John Porter
- Re: RFC 84 (v1) Replace => (stringifying comma) with ... Jeremy Howard
- Re: RFC 84 (v1) Replace => (stringifying comma) ... Jarkko Hietaniemi
- Array storage (was Re: RFC 84 (v1) Replace =>... Jeremy Howard
- Re: Array storage (was Re: RFC 84 (v1) Repl... Jarkko Hietaniemi
- Re: Array storage (was Re: RFC 84 (v1) ... Dan Sugalski
- Re: Array storage (was Re: RFC 84 (v1) ... Jeremy Howard
- Re: Array storage (was Re: RFC 84 (v1) Repl... Stephen P. Potter
- Re: Array storage (was Re: RFC 84 (v1) ... Jeremy Howard
- Re: RFC 84 (v1) Replace => (stringifying com... Peter Scott
- Re: RFC 84 (v1) Replace => (stringifying com... John Porter