Front page | perl.perl5.porters |
Postings from December 2012
On Thu Dec 13 07:19:45 2012, tlhackque wrote: > > This is a bug report for perl from tlhackque@yahoo.com, > generated with the help of perlbug 1.39 running under perl 5.14.3. > > > ----------------------------------------------------------------- > [Please describe your issue here] > > Functions using 'exec' (at least exec, system qx) generate warnings if > 'use warnings;' is in effect. > > This isn't a bad thing - but the fact that the documentation for these > functions doesn't mention this is. My impression is that for most of the built-in functions there is no specific discussion of how they work under "use warnings" -- nor would I expect there to be. So it's not clear to me why this is somehow a bigger documentation problem for 'system' and 'exec' than for other built-ins. > Especially since the documentation emphasizes that one really should > 'use warnings' everywhere. > (And one should. And I do.) > > The only documented exception from these functions is 'die' on tainted > input. > > Please update these functions to indicate that: > o They generate call warn() on errors running the command if 'use > warnings' is in effect; and > o The category to disable these warnings (if, for example one is > checking the return status & expects failures in some environments) > is "no warnings 'exec';" > > Actually, it would be really helpful if every function that registers > with 'use warnings' would include similar info in its > documentation. > > It took rather some tracking down - and some guesswork - to solve an > issue caused by this behavior. Even though I did read the manual > (and the book and the perldoc and the perl website...) > > Thanks. --- via perlbug: queue: perl5 status: new https://rt.perl.org:443/rt3/Ticket/Display.html?id=116080Thread Previous | Thread Next