Hi Marcus, thanks for replying so quickly.
Exiting perl in such a manner, or indeed in any program written in any
language, without the program explicitly doing so itself, would be considered a
critical bug. I am surprised to hear that this is what happens in C also.
Surely, it would be considered a bug in C. I fail to see how it can be
considered a feature in any regard.
Show quoted text>> It does not die, so you can't catch it in an eval.
>
> Sorry. But why would anyone care? Does it do any harm to call
> closelog() without an open syslog connection?
Well, I care, because it just happened for me. Apparently it does the most harm
possible - program exits. If a function provided by any module might cause your
program to quit, then we would have to put a trap around each call of the
function. That would be fair enough if it were documented, I guess, but the
fact that I can't even catch it in an eval is distressing.
If you're still reluctant to fix this, might I suggest that you put a note
about it on the CPAN page?
--
.