Mike Schilli [mailto:[EMAIL PROTECTED] wrote: > > On Thu, 28 Jun 2007, Lee Goddard wrote: > > > Please could Log/Log4perl/Config.pm line 619 offer a stack backtrace as > > well as barfing? > > > > My current project has four config files, several potential initialisers > > (bad idea, I know) and reports only via e-mail, since it is part of a > > MTA process. > > Dumping a stack trace by default might be confusing to the casual L4p > user, but you can certainly use the following: > > use Log::Log4perl; > use Carp; > > eval { > Log::Log4perl->init(...); > }; > > if($@) { > confess($@); > } > > Would this work for you?
That's what I've ended up with, but I just thought it logical that an error generated by an operator error, such as wrong path to a config file, would Carp::croak, to let the user know from whence their error came.... Lee ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ log4perl-devel mailing list log4perl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/log4perl-devel
