--- Rich Morin <[EMAIL PROTECTED]> wrote:
> Given that the Perl executable may be located in
> any of several places, hard-coding a path into
> the shebang line isn't all that great an idea.
> The following will always give you the version
> of perl that comes first on your search path:
>
> #!/usr/bin/env perl
That's a cool suggestion, but I had a couple
questions. Is it good to hardcode the path to `env`,
or just not as bad as hardcoding the path to `perl`?
And how is this different/better than just using
"#!perl"?
Second, and somewhat more personal, I have an
alternate perl (5.8.1) at /usr/local/bin so as not to
clobber the default system perl (5.6.0). I also have
my path set up so the system default is the first in
the path (meaning I need to either type
`/usr/local/bin/perl` or `perl5.8` to get my perl). Is
this path set up necessary to avoid munging with
things that use the system's perl, or are things that
use the system's perl set up to bypass the path?
__________________________________
Do you Yahoo!?
Yahoo! Domains – Claim yours for only $14.70/year
http://smallbusiness.promotions.yahoo.com/offer
