On Thu, Aug 11, 2005 at 01:52:35AM -0700, Nicholas Clark via RT wrote:
> On Wed, Aug 10, 2005 at 12:21:49PM -0400, Ed Ravin wrote:
>
> > I submit that this is a design bug - no other syslog() library behaves
> > this way, especially not the C library that Syslog.pm is based on.
> > Sys::Syslog::syslog() should return an error and let the user deal
> > with it (which would be an improvement over the C version, which has
> > no defined return values).
>
> One way of implementing in error return in perl is throwing an exception.
>
> We may not agree whether this is the most appropriate design paradigm in
> this case, but it's definitely a perlish way of doing things, even if it's
> not a syslogish way.
In that case, we have a documentation bug - the fact that Sys::Syslog might
crash the calling program with croak() is not mentioned in its man page.
Would you accept patches for a "nocroak" or "nofatal" option to be used
in Sys::Syslog::openlog() to disable the fatal exit behavior?
-- Ed
