NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Put it in a module! (Score:2)
But since lots of people don't use the command line (they hit Perl via a batch script or similar) now I might also need to hijack perl.exe entirely to deal with it (except that breaks things that do pass-through code to child Perl's for process isolation reasons).
Eh, no, you don't have to patch perl.exe. Instead, put it in a module. Just like diagnostics [perl.org] does nothing but explaining warnings and errors better.
You can load this module on the command line using -M, or you could set an environment variable like PERL5LIB, so it gets used in every Perl script that gets run from the batch file.
Re:Put it in a module! (Score:1)
If the executable supported localization and translation files, swapping in other error messages would be easier. (Replacing them entirely might not be as easy though.)
Reply to This
Parent