On 1 March 2018 at 08:36, Jeff King <peff@xxxxxxxx> wrote: > On Wed, Feb 28, 2018 at 05:51:14PM +0100, demerphq wrote: > >> I would look into putting it into a module and then using the PERL5OPT >> environment var to have it loaded automagically in any of your perl >> scripts. >> >> For instance if you put that code into a module called Git/DieTrap.pm >> >> then you could do: >> >> PERL5OPT=-MGit::DieTrap >> >> In your test setup code assuming you have some. Then you don't need to >> change any of your scripts just the test runner framework. > > That's a clever trick. > > It's not clear to me though if we just want to tweak the programs run in > the test scripts in order to get test_must_fail to stop complaining, or > if we consider the unusual exit codes from our perl-based Git programs > to be an error that should be fixed for real use, too. Yeah, that is a decision you guys need to make, I am not familiar enough with the issues to make any useful comment. But I wanted to say that I will bring this subject up on perl5porters, the exit code triggered by a die is a regular cause of trouble for more than just you guys, and maybe we can get it changed for the future. Nevertheless even if there was consensus it can be changed it will take years before it is widely distributed enough to be useful to you. :-( Ill be bold and say sorry on the behalf of the perl committers for this. Perl is so old sometimes things that used to make sense don't make sense anymore. cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
