develooper Front page | perl.perl5.porters | Postings from May 2016

Re: 5.24.0 + cpan

Thread Previous | Thread Next
May 17, 2016 11:18
Re: 5.24.0 + cpan
Message ID:
On Mon, May 16, 2016 at 08:52:52PM +0100, Zefram wrote:
> Aaron Crane wrote:
> >Assuming that we retain the behaviour of honouring "perl6" in a
> >shebang line, how about this change?
> That retains the rather crap behaviour of looking only at the *first*
> instance of "perl" on the line.  It would make more sense to look for
> "perl6" either at *all* instances of "perl" (requiring all to be "perl6"
> to enable chaining) or just in the basename part of the interpreter path.
> But who's to say that "perl6" meaning Perl 6 won't be followed by a
> version number?  Do the perl6 folks have a convention for that?
> But I go back to what I said about this last year, when the "perl6"
> change was originally proposed: the #! hack is obsolete.  We should either
> leave it totally unchanged (as it was pre-5.23) or remove it entirely.
> Changing it for perl6 is just inviting nasty surprises.

I think I agree with Zefram.

Do we have any statistics on how useful the #! hack is? Who uses it
knowingly? Is there really much benefit for a feature where one can
do "perl some-non-perl-script" and have perl exec the right thing?
I've a hard time imagining people getting hurt if this feature
will be dropped.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About