Paul "LeoNerd" Evans <leonerd@leonerd.org.uk> wrote on Wed, 03 Jun 2015 14:25:29 BST: > 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'; Which is basically what use warnings qw(FATAL all); turns out mean: it invites future breakage. --tomThread Previous | Thread Next