On Wed, 3 Jun 2015 09:15:04 -0400 Ricardo Signes <perl.p5p@rjbs.manxome.org> wrote: > 'all' can remain available in warnings.pm and be made available in > strict.pm, although I'd personally discourage turning 'all' on, > except maybe in private testing, for the sake of forward > compatibility. Yes, some existing code may be affected because it > says "use warnings 'all'" explicitly, but we already add new kinds of > warnings, we're just very circumspect in doing so -- as we'd continue > to be in adding default warnings. No existing code does "use strict > 'all'" because there is no "all" yet. I'd put massive warnings around use strict 'all'; because it is effectively saying use strict 'I-am-happy-for-any-future-version-of-perl-to-break-my-program'; > With this in place, we can add more strictures and less-critical > warnings without the worry that they're breaking old programs, > because old programs won't have them enabled. This sounds like an excellent idea; we do have a number of pragmata sitting around that would make good strict.pm candidates... +1 from me -- Paul "LeoNerd" Evans leonerd@leonerd.org.uk http://www.leonerd.org.uk/ | https://metacpan.org/author/PEVANSThread Previous | Thread Next