On Jul 26, 2004, at 12:26 AM, Rich Morin wrote:
#!/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 outpu
#!/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 s
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--
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
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 Apple is
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 - I
> Which is not really portable with command line options, due to how
> env(1) works on OS X:
>
> $ #!/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
* Paul McCann <[EMAIL PROTECTED]>
> That would probably have been the use of the "env" utility: instead of
>
> #!/usr/bin/perl
>
> or similar you make the first line of your scripts read
>
> #!/usr/bin/env perl
Which is not really portable with command line options, due to how
env(1) works on
Hi ~wren,
you wrote...
> Sorry if this is off-topic, but I seem to recall
> sometime fairly recently (less than a year, more than
> a few weeks) someone mentioned a way to "autofind" the
> path to perl on the shebang line so you don't need to
> hardcode the path. I can't seem to find the p
Sorry if this is off-topic, but I seem to recall
sometime fairly recently (less than a year, more than
a few weeks) someone mentioned a way to "autofind" the
path to perl on the shebang line so you don't need to
hardcode the path. I can't seem to find the post in
the archives. Does any one remember
