develooper Front page | perl.perl5.porters | Postings from April 2021

Re: on changing perl's behavior

Thread Previous | Thread Next
From:
Todd Rinaldo
Date:
April 8, 2021 21:18
Subject:
Re: on changing perl's behavior
Message ID:
DDCB72D1-67FA-4DB9-B5E9-25259D320A9C@cpanel.net


> On Apr 7, 2021, at 10:31 AM, Christian Walde <walde.christian@gmail.com> wrote:
> 
> On Wed, 07 Apr 2021 15:26:55 +0200, Nicholas Clark <nick@ccl4.org> wrote:
> 
>> So the point that I'd like to make is that there are *some* things that
>> might be removed to simplify the internals and reduce the support burden,
>> but *most* existing things don't get in the way, at least at runtime.
> 
> Thanks for adding more detail. I really appreciate that effort to provide tangible evidence for this. :)
> 
> A small addendum:
> 
> I think it's fine to change the defaults in these cases:
> 
> 1. when the behavior is a security risk
> 2. when the behavior is outright broken and subverts expectations and optimally also documentation
> 3. when actually finding examples of anybody using the behavior is nearly impossible
> 
> I think your examples all fall under 3.?
> 
> Outside of that, when a huge win can be demonstrated, stuff should be removed, but then i'd prefer it be done by way of deprecating that specific dialect.


I would argue (though it's hard to search for "format" in the issues list) that being able to close 50+ cases would be nice if we could just say: "Formats are removed. this issue is now irrelevant." 

For me all of that would fall under #2.

Todd
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