[log4perl-devel] should Log::Log4perl::Config::config_read call die ?

[<lei...@hp...>]

I am not sure if this has been raised before, the sourceforge mail list
browse doesn't have a search function, so I just checked the last 100
messages.
 
I suppose I would call this more an issue of style - I have issues with any
library that exits on me. I would prefer a library told me 'sorry I cant
help you' and let me decide on the flow from there.
 
This arose because I sometimes execute .t files from within the t directory
(especialy if I am writing a .t file in an editor - I use xemacs and run
mode-compile on the .t file) - to get around the fact that the Log4perl
config file is one directory up I usually provide a symlink to it inside the
t directory.
 
An eval could help - in fact there are many 'workarounds' - but I still feel
calling die is wrong.
 
Are there any plans for this behaviour to be revised in the future ??

Leif Eriksen
Developer
HPA - IT Development
+61 3 9217 5545
lei...@hp... 

 



**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are
addressed.  If you received this e-mail in error, please notify
the HPA Postmaster, pos...@hp..., then delete 
the e-mail.

This footnote also confirms that this e-mail message has been swept for
the presence of computer viruses by MimeSweeper.  Before opening or
using any attachments, check them for viruses and defects.

Our liability is limited to resupplying any affected attachments.

HPA collects personal information to provide and market our services.
For more information about use, disclosure and access see our Privacy
Policy at www.hpa.com.au
**********************************************************************