in reply to Log::Any with die and carp

Hi, as you no doubt know Log::Any's approach is very minimalistic and I don't think you can really expect it to do anything other than send messages to the logger.

So I think your approach may be the best you can do on the producer side. But, do you really need to output with Carp functions if you are going to log the longmess at level critical? Couldn't you simply document that the log will contain the stacktrace and push responsibility onto the consumer to, well, consume it, and then just die tersely?

Hope this helps!


The way forward always starts with a minimal test.

Replies are listed 'Best First'.
Re^2: Log::Any with die and carp
by learnedbyerror (Monk) on Dec 17, 2018 at 13:44 UTC

    Thanks for your response. I was hoping that I missed something :(

    I think you are right regarding logging longmess and die terseley

    Thanks again!, lbe