Re: Re: Strict, my and warnings

[demerphq]

I never need to switch off warnings anywhere,

Interesting. There a bunch of modules that I routinely use that produce warnings under -w. In fact I spent a day trying to figure out what I was doing wrong, only to realize that my colleague had slipped a -w into the script and that nothing was wrong. (Win32::Eventlog is the latter mentioned module)

Personally I think that the late introduction the warnings modules and its consequent slow takeup and usage was one of the few serious language errors that was made in the earlier versions of perl. (Strong words I know, but im entitled to an opinion :-)

I suspect that perl6 will have a quite powerful warning and strictures structure from the get-go as a lesson learned from this.

--- demerphq
my friends call me, usually because I'm late....

[Aristotle]

Slap the module author(s) on the wrist. Lexically disabling warnings will work under -w and of course you can localize $^W as we used to do. So I don't see any excuse not to take the proper action to disable them as needed if you're intentionally doing something that may raise warnings. My take on this is fairly rigid. There are times that call for not complying with warnings or strict, but you should at least have the decency not to force that choice unto whoever is using your code as well.

File a bug report or complain to the author by email.

Makeshifts last the longest.