Well, i can see your idea about strict being useful for sure. But for me the one thing id like to see is that @{undef} returns 0 or () in a rhs context and not throw an error. If I have to twiddle an option then fine. If that means it gets autovivified then thats fine too. Although id prefer that things dont get autovivified on read. Even multilevel accesses.

:-)

--- demerphq
my friends call me, usually because I'm late....