[Xml-compile] Re: Log::Report modes

[Mark Overmeer]

* Karen Etheridge (perl at froods.org) [121017 21:15]:
> On Wed, Oct 17, 2012 at 11:08:35PM +0200, Mark Overmeer wrote:
> > * Karen Etheridge (karen at etheridge.ca) [121017 21:03]:
> > > > Log::Report function try() will catch it.
> > > 
> > > I'm already using TryCatch's try() - is there another way of suppressing
> > > Log::Report warnings?
> > 
> > try() is just an eval "".  With the 'reasons' parameter, you can select
> > what you want to see in $@, just like the other dispatchers.
> 
> Not really - try() should be much more than just a bare eval. e.g. see all
> the caveats listed at https://metacpan.org/module/Try::Tiny#BACKGROUND -
> good exception handling is actually quite difficult to do.

Of course I know that.  Log::Report::Dispatcher::Try() is quite
sofisticated, a bit smarter than Try::Tiny.  But many of the same
caviats.

> > I would not mind a rare additional error message every once in a while
> > (syslog is patient).
> 
> I mind :) - it means I have to set up a separate error channel to handle
> these situations.  I'd rather just turn it off, as I'm going to see what
> the eventual result of the request was, when I examine $answer and $trace.

When it does not show up in the trace as well, then it certainly is
an bug.  I'll have a look.
-- 
Regards,

               MarkOv

------------------------------------------------------------------------
       Mark Overmeer MSc                                MARKOV Solutions
       Mark at Overmeer.net                          solutions at overmeer.net
http://Mark.Overmeer.net                   http://solutions.overmeer.net