# from David Nicol
# on Wednesday 03 September 2008 13:29:
>Furthermore, you're enforcing a stricture, rather than enhancing Carp.
> Here's a briefly considered suggestion:
>
> perl -Mstrict::sigdie yourprogram.pl
>
>Maybe some day this will be a best practice:
>
> use strict;
> use strict::sig::die;
>
>calling it strict::sig::die opens up the strict::sig:: space for
>future development of pragmata that enforce strictures about other
>entries in %SIG, too.
True, though I would rather that it not need to be a standard practice.
Any code I write isn't going to install a global die handler without
really good reason, so it is more useful in checking for action at a
distance than watching over me. But: Put it in all of your tests or
as a harness option? Sure. Wherever you're concerned about weird
stuff creeping in.
But put it in all of your cpan modules? No. That's just too much
nannyism and because of the global-at-a-distance nature it would be at
least as bad as the thing it is meant to detect.
David Cantrell suggested Devel::NoGlobalSigDie, which fits, but I think
that's maybe a lot to pound in after "-M" (or -d: for that matter.)
What about Devel::no::sigdie? I get his point about the global, but
maybe it could just be an option. Devel::NoSigDie is too much
shifting?
--Eric
--
"...the bourgeoisie were hated from both ends: by the proles, because
they had all the money, and by the intelligentsia, because of their
tendency to spend it on lawn ornaments."
--Neal Stephenson
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
