Which is not really portable with command line options, due to how
env(1) works on OS X:
$ test
#!/usr/bin/env perl -wl
print hello world
$ ./test
env: perl -wl: No such file or directory
That is both against the documentation (env(1)) and the UNIX spec,
so I think a bug report to
On Jul 25, 2004, at 4:57 AM, Jarkko Hietaniemi wrote:
That is both against the documentation (env(1)) and the UNIX spec,
so I think a bug report to Apple is in order. (Actually, env as such
seems to be working okay, so it is more likely a bug in the #!
processing.)
It's not unique to Mac OS X -
On Jul 25, 2004, at 1:57 AM, Jarkko Hietaniemi wrote:
Which is not really portable with command line options, due to how
env(1) works on OS X:
$ test
#!/usr/bin/env perl -wl
print hello world
$ ./test
env: perl -wl: No such file or directory
That is both against the documentation (env(1)) and the
On Jul 25, 2004, at 2:09 PM, Edward Moy wrote:
This is one of those historical worts.
I can ferment it to make beer? Cool! ;-)
sherm--
Dear Warren, Marc, Clark, Eddy:
SoccerDirector is ready for the division heads to use. Writing the User Guide
resulted in some more features being added. I think I probably spent more
time on it than I should have, so I'm happy to hand it off now and move on to
other projects.
I've uploaded
Hi,
As a person who subscribes to the [EMAIL PROTECTED] mailing list, I was
struck funny by the your email to Warren, Marc, Clarc, and Eddy. I
could be wrong, but... I think this email might not have been for all
of us on the list. Am I wrong? Just didn't want anyone to get into deep
weeds
#!/usr/bin/env perl -wl
Looking in the Camel, I'm not sure what the -l flag is supposed to
be doing for you. You're not using it with -n or -p, so it isn't
auto-chomping the input lines; you didn't give it an argument, so
it isn't changing the output line terminator. So, what's it for?
My Perl
