On Tue, 2004-03-30 at 06:22, Robert Collins wrote:
> On Tue, 2004-03-30 at 13:47, Mary Gardiner wrote:
> > Hi folks,
> >
> > I'm accustomed to starting my various Python and Perl files with:
> >
> > #!/usr/bin/env python
> >
> > or
> >
> > #!/usr/bin/env perl
> >
> > to deal with the situation where the python or perl binary lives in
> > different places on different systems (please don't reply suggesting I
> > just move it or just install Debian or something, some of us still work
> > in archaic environments where we don't have root on servers we use!!!!)
> >
> > However, you can't pass arguments to whatever you're invoking, thanks to
> > the limits of the #! interpretion ("#!/usr/bin/env perl -w" at the top
> > of a file causes a search for a binary named "perl -w").
>
> Are you sure? env --help suggests that it doesn't.
Certainly does on my box:
$ cat t
#!/usr/bin/env perl -w
$ ./t
/usr/bin/env: perl -w: No such file or directory
Maybe I need a more cutting-edge env.
j.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
