Front page | perl.perl5.porters |
Postings from November 2015
On Mon, Nov 23, 2015 at 05:56:04PM +0100, Eirik Berg Hanssen wrote: > On Mon, Nov 23, 2015 at 5:43 PM, Abigail <abigail@abigail.be> wrote: > > > Forcing warnings upon users who have choosen not to enable warnings > > doesn't sound to me as even remotely user friendly. > > > > Not all who have not chosen to enable warnings have chosen not to enable > warnings: > > If warnings were on by default, and had to be explicitly disabled, I'd > grant you that point. > If everyone who doesn't enable warnings didn't chose to do so, you may have a point. Taken away *choice* from *everyone* just so someone somewhere may have a benefit doesn't sound me as a even remotely user friendly. Besides, if that's the argument, why just this warning? Why not make every warning mandatory? I'd say issue a deprecation warning once we have a schedule were the feature is removed, and replaced by something else. Deprecation does not mean "I don't like the style, so other shall not use it". That's not what Perl is about. AbigailThread Previous | Thread Next