Re^2: Error Reporting from Module

If you go that route you might look at Log::Log4perl or Log::Dispatch rather than reinventing existing wheels.

The cake is a lie.
The cake is a lie.
The cake is a lie.

Comment on Re^2: Error Reporting from Module

Replies are listed 'Best First'.
Re^3: Error Reporting from Module by tobyink (Canon) on Oct 09, 2019 at 14:44 UTC
I've always found those sorts of things are more oriented around application-level logging rather than a module reporting errors to its caller, but my experience with them is pretty minimal. toby döt ink	[reply]
Re^4: Error Reporting from Module by Fletch (Bishop) on Oct 09, 2019 at 15:15 UTC
Very valid point; you then tie your users into said framework. I've grown to like L4p but then I've been recently mucking with stuff in spark JVM land from clojure and it's pretty much a given that something will have set up sl4j (or some other compatible logging mechanism) and so using that is just the way things are done and that's probably coloring my thinking. The cake is a lie. The cake is a lie. The cake is a lie.	[reply]