If disabling the warning altogether doesn't work, the next best thing would be to not use the module at all IMHO. The doc on Fatal Warnings is quite explicit about the fact that use warnings FATAL => 'all'; is a bad idea. One obvious replacement for this module is to just copy it without the problematic line, since it's a pure perl module.
I would actually avoid just catching the exception though. Because the exception means the function add_child has been interrupted before finishing, so the state of the object is not guarranteed to be correct (eg: _fix_width hasn't been called at all).
Edit: or just let the author fix his module. I should be more patient and not always jump to the fastest fix so carelessly. Thanks to stevieb and ron.savage for the actual correction :D
In reply to Re: Turn off FATAL warnings in 3rd party module
by Eily
in thread Turn off FATAL warnings in 3rd party module
by bliako
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |