A NUL byte is illegal in filenames on most OSses
And so is the pipe in Windows, yet.
>perl -wle"open my $fh, '>', 'a|' or die $!" Invalid argument at -e line 1. >dir /b a File Not Found
It doesn't behave any different from the underlaying system functionality.
So I'm expected to know the underlying function call used for each system and ignore the documentation?
There's actually a documented 'trick' that makes use of NUL characters (if you want to open a file containing trailing whitespace - this predates 3-arg open).
People use my ... if ...; too even though it's documented to be invalid Perl. The solution is to provide a better alternative (state vars and 3-arg open).
Perl core developers may be smart, but there are only a few.
You've been defending the behaviour up until now, yet you now say it's only present because noone's gotten around to fixing it?
Is that even the case, or did they reject a fix?
In reply to Re^2: Why do poisoned null attacks still work ?
by ikegami
in thread Why do poisoned null attacks still work ?
by pubnoop
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |