develooper Front page | perl.perl5.porters | Postings from December 2017

[perl #108778] no warnings "module name"

Father Chrysostomos via RT
December 17, 2017 20:00
[perl #108778] no warnings "module name"
Message ID:
On Wed, 13 Dec 2017 12:32:58 -0800, wrote:
> Father Chrysostomos via RT wrote:
> >At the very least, can we make register the overload
> >category, or make overload a core category?
> If we do that for overload, why not for others?  Where do we draw
> the line?, like strict and warnings, is a core feature.  The functionality these modules provide is not actually implemented in the modules themselves, but is part of perl.

That registers its own warnings category and uses warnings::warnif is just an implementation detail.  Its warnings are even listed in perldiag under the ‘overload’ category.

Hence, I think it is sufficiently part of the language itself, and not just another module.


Father Chrysostomos

via perlbug:  queue: perl5 status: open Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About