Austin Hastings wrote:
There is no reason why primitive-typed arrays can't have a default. It
is the confusion of "default" with "undef" that is causing this
problem.
If I have:
my int @a;
print @a[4];
What comes out?
Notice, there's no "is default(woo-woo)" in there. Just a plain old
primitive array.
I imagine that each primative type will have a default default :-) int 0 str '' num 0.0 etc.
and if we define a prop "is no_default" then you get what ever junk happens to be in memory. (this for even more speed) -- Mark Biggar [EMAIL PROTECTED]
