The diamond operator, however, happily uses two-argument open to processes the contents of the @ARGV array, which by default contains the command line arguments supplied by the user. This means, that an argument "< foo" makes my program read a file named "foo", an argument "> foo" makes it clobber a file named "foo", and an argument "rm * |" makes it run a program that on my platform happens to remove every file in the current directory.
I don't get this.
You (or someone) is using a "unix filter" perl script at the command line.
You are concerned that you (or they) might accidentally (or maliciously) type a dangerous command in place of a filename as input to that script.
What is to stop you (or they) from entering that command directly into the command prompt you (or they) are using?
In reply to Re: Good-bye Unix filter idiom
by BrowserUk
in thread Good-bye Unix filter idiom
by martin
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |