develooper Front page | perl.perl5.porters | Postings from January 2012

Re: Shebang line parsing mystery

Thread Previous | Thread Next
From:
Eric Brine
Date:
January 18, 2012 12:54
Subject:
Re: Shebang line parsing mystery
Message ID:
CALJW-qEH+C6m1TRGJW5cNCfxsNX+-Ej6+USViRuso=LTnStQdw@mail.gmail.com
On Wed, Jan 18, 2012 at 10:22 AM, Rafael Garcia-Suarez <rgs@consttype.org>wrote:

> On 18 January 2012 16:10, Nicholas Clark <nick@ccl4.org> wrote:
> > On Tue, Jan 17, 2012 at 03:34:07PM +0100, Rafael Garcia-Suarez wrote:
> >> As for the decision of deprecating (or cutting off) the whole
> >> exec-what's-on-the-shebang functionality, I'll wait for informed
> >> advice.
> >
> > Is there any way to work out who is using this?
> >
> > I'm a bit stuck as to how to measure it. And really without any feeling
> for
> > whether it's useful to anyone, I find it hard to have an opinion about
> it.
>
> Also, who uses the exec-what's-on-the-shebang feature nowadays ?
>
> > The code is (effectively) stable. Is it getting in the way?
>
> It's surprising and undocumented. I could document it. But I fear that
> the number of users for that hidden feature is 0.
>

The feature is documented. From perlrun:

If the #! line does not contain the word "perl", the program named after
the #! is executed instead of the Perl interpreter. This is slightly
bizarre, but it helps people on machines that don't do #! , because they
can tell a program that their SHELL is */usr/bin/perl*, and Perl will then
dispatch the program to the correct interpreter for them.

It's just "indir" that's not documented.

- Eric

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About