Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I read this about the same way I read much Perl documentation, written soon after somebody had a good idea and before much time was alotted for serious reflection on the idea. Like the prominent notice that was added to "use vars" saying that 'our' is better. Actually, there are good arguments for ways in which vars.pm is better than 'our'. Or documentation that "use warnings" is better than -w. perllexwarn says "use warnings" is "more flexible" than "-w" and $^W. Actually, warnings.pm is just different. It can be used to do things that can't be done with -w/$^W but it also can't do many things that can be done with -w/$^W. And I find -w and $^W to be better suited for writing modules than "use warnings" (while "use warnings" is sometimes better when writing scripts). There could certainly be some improvements made to how $SIG{__DIE__} handlers nest with eval and other $SIG{__DIE__} handlers, but I would be quite surprised if p5p fulfilled that ancient threat and broke Devel::EvalError and lots of other reasonable uses. - tye In reply to Re: Deprecated use of $SIG{__DIE__} is useful (haste)
by tye
|
|