Re^3: Stumped by a warning (carp)

The google results say that it is likely a flaw in something generated by h2xs.

The reason you didn't get details about where the warning came from is because you overrode the __WARN__ handler, probably by doing "use diagnostics;". So comment out that line and you'll likely be told not only what *.ph file is generating the warning but also what module pulled that file in (and what module pulled that module in, etc.).

(This is yet another example of why it might be a very good idea for eval to suppress warnings, especially "mandatory warnings".)

- tye

Comment on Re^3: Stumped by a warning (carp)

Replies are listed 'Best First'.
Re^4: Stumped by a warning (carp) by Wiggins (Hermit) on Nov 16, 2012 at 17:52 UTC
I restored the 'use warnings;' and 'require /sys/ioctl.ph;' and then comment out the 'use diagnostics;'. The warning did not display . Maybe there can be too much introspection. It is always better to have seen your target for yourself, rather than depend upon someone else's description.	[reply]
Re^5: Stumped by a warning (carp) by tye (Sage) on Nov 16, 2012 at 18:47 UTC
'use warnings' won't enable warnings in other lexical scopes (use -w instead if you want). But it sounds like you already know that sys/ioctl.ph is where the warning is coming from. - tye	[reply]