I'm surprised that Perl uses this way to open files with magic ARGV.

Why? This feature existed long before open had 3 arguments, why would it suddenly change.

And nobody in his right mind would expect the magic <> to be actually implemented in Perl. Do you? I think, not. C provides far less dangerous library functions.

And nobody in his right mind would expect the magic <> to be actually implemented in Perl. Do you? I think, not. C provides far less dangerous library functions.

Now that's just ridiculous. Larry and the perl 5 porters who wrote it expected it to behave that way, as would anyone who read the documentation.

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy.

Larry and the perl 5 porters who wrote it expected it to behave that way, as would anyone who read the documentation.

But is it the sane thing for it to do? I think not. Neither does any of the other opponents, I would think (tye, Juerd).

The most sane thing to do would be to drop support for 2 argument open, putting mode and file path into one argument, completely.

Why? This feature existed long before open had 3 arguments, why would it suddenly change.

I didn't think it would use normal perl open internally. Given that two-arg open enables command execution and that at that time only one- and two-arg open existed, I think it should have opened files by other means.

But we live in a world that has three-arg open now. It's time to change, imo.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }