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

Re: pop @INC (".")

Thread Previous | Thread Next
From:
demerphq
Date:
March 8, 2012 23:27
Subject:
Re: pop @INC (".")
Message ID:
CANgJU+VUWykJYRWQiss6ZVNDf05F5PK2am0pxDB-xBQk8aGhpw@mail.gmail.com
On 9 March 2012 01:24, Tom Christiansen <tchrist@perl.com> wrote:
>> I don't consider it a bug. @INC has contained "." since the dawn of time.
>> I bet there are tons of script happily running on servers everywhere,
>> doing their job, and depending on "." being in @INC.
>
>> Now, todays thinking may be that it's better not to have "." in @INC. And
>> while I won't argue with that, I don't think we should remove "." from
>> @INC.  IMO, breaking something that works now outweighs any potential
>> advantages of not having "." in @INC by default.
>
> Absolutely.
>
> You cannot change running programs out from under them.  This
> egregious break with backwards compatibilty will break other
> people's programs.  I guarantee it.  I also guarantee that doing
> so will be a complete disaster.

I don't have much of an opinion on the subject in question, but I
absolutely disagree with this position as policy.

Releasing a new perl that breaks some form of backwards compatibility
is not "changing running programs out from under them". The user has
to upgrade, a conscious act, and they should look at the change log
and consider the implications and act accordingly.

We are absolutely NOT chained to support everything we supported in
the past. We tend to do so, and certainly much prefer to do so, but we
are not obliged to do so. If breaking backwards compatibility is in
the best interest of Perl then that is what we will do.

cheers,
Yves


-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

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