How about adding use MyModuleWhichExports_die; where MyModuleWhichExports_die exports a custom sub die { } which does whatever you need it to do?

Thanks for that. I did not realize you could overwrite Perl's built-in functions that way. This is pretty much what I am looking for.

Quick (possibly dumb)question:
Is it possible to inline MyModuleWhichExports_die in the main program and have it "export" the custom die() function?
e.g.:

package MyModuleWhichExports_die;
# Something like Export's "@EXPORT" list here
sub die {
    CORE::die "New and improved!: @_";
}

package main;
die "I want to be prefixed with 'New and improved'";
[download]

I know I can do that by using the fully qualified name of my custom die() (MyModuleWhichExports_die::die), but that defeats the whole purpose of writing a wrapper so I don't have to change my original die() calls in the code

Is it possible to inline MyModuleWhichExports_die in the main program and have it "export" the custom die() function?

Sure, why not , as long as its loaded before all the other things that load it ... go fish :)

Import::Into, ex::override ,Override the open builtin globally.. redux, Re: Selectively importing warnings (works), Re: how to make lexical pragma global, hints ( pl_hints $^H %^H ), taint::all (package taintall)

and some of these

perl5, perl5::ingy
ToolSet
Syntax::Collector
Toolkit
rig
see perlrun#PERL5OPT , PERLLIB, PERL5LIB
sitecustomize under perlrun#* f*
how to make lexical pragma global, hints ( pl_hints $^H %^H ), taint::all, Re: batch 'use' possible? (perl5.pm Toolset.pm, Syntax::Collector , Toolkit.pm, rig.pm, sitecustomize.pl, PERL5OPT )( load multiple commonly-used favorite modules in a single import expression )

export into / Import::Into

 

:D

Maybe like

sub CGI::die { log... CORE::die() }
sub pachage::package::die { log... CORE::die() }
sub shamalama::lamma::die { log... CORE::die() }
use CGI;
use pachage;
use shamalama::lamma;
[download]

Or how about replacing each die with LOGDIE from use Log::Log4perl qw(:easy);

That is what I am trying to avoid. The whole raison d'être of this is to seamlessly add Log4perl to an existing script without having to go hunt down and change all the die() (and warn()) calls in the code.

without having to go hunt down and change all the die() (and warn()) calls in the code.

But you don't have to do that, you just have to add use whateveritwasthatexportsdie;; to the top of each module ... no search/replace