I have always felt that keeping it the same as shell scripting was a handy
thing, especially when I have been teaching it to others. It also makes
the ol' perl5
open FH, "|/usr/bin/foo";
make a lot more sense. Using something like
open "p", "/usr/bin/foo";
just wouldn't have the same ring to it. Aside from which, it gets even worse when you consider how you would have to change:
open FH, "/usr/bin/foo|";
My personal preference is for:
$in=open :r "|/usr/bin/foo";
$out=open :w "|/usr/bin/foo";
$both=open :rw "|/usr/bin/foo";The pipe would be legal on either side of the string. This would still allow the often-useful "type a pipe command at a prompt for a file", while matching the trait-based syntax suggested elsewhere.
-- Brent "Dax" Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker
Oceania has always been at war with Eastasia.
