|Do you know where your variables are?|
I feel with you, I'm not happy with their decision either, and some discussion turn out rather frustrating on p5p.
It's a feature so magic (and so little known) that it can be considered a security hazard. IMHO.
Even though we can't convince them, we can still do something about it: propose documentation patches. I'd like to write some, but in the last two weeks I haven't got around to anything perlish, so I don't think I'll get around to it any time soon.
If nobody gets around to it, maybe we should write a patch against pod/perltodo.pod in perl.git to mark it as a TODO item.
(Update: patch submitted, and it has been applied already.)
One more half off-topic note about p5p: Changes that go rather deeply are hard to get approved. That's not a priori bad, because backwards compatibility is very valuable. Still it means that many things that (again, IMHO) need fixes very badly don't get fixed, or only very, very slowly.
That's part of the reason why Perl 6 is needed: Both as a clean break, and as a vision. Politically it's much easier to backport a Perl 6 feature to Perl 5 than to invent a new, equivalent feature in Perl 5 itself. Sadly that doesn't work when backporting sanity to Perl 5...
In reply to Re^3: magic-diamond <> behavior -- WHAT?! (sanity)