Exception Handling

(I apologise in advance for the on-topic[1] nature of this
mail)

A couple of years ago, I can remember sitting in Fotango's
office  
listening to Mark Fowler give an interesting talk about the
various  
Perl exception handling modules. As I recall it ended by
saying they  
all had their faults which is why he had written another
one.

We're currently contemplating changing the exception
handling for the  
project I'm maintaining and Mark's talk would be a good
introduction  
to the issues we need to consider. Unfortunately, it doesn't
seem to  
be on the tech talk page on the web site[2].

So, does anyone have either a) a link to that talk or b) an 

interesting opinion on which exception handlers I should be 

investigating?

Cheers,

Dave...

[1] Or is that "off-topic"? I can never remember.
[2] http://bond.pm.org/tec
h_talks/

-- 
site: http://dave.org.uk/
blog: http://blog.dave.org.uk/

On 11/07/07, Dave Cross <davedave.org.uk> wrote:
>
> So, does anyone have either a) a link to that talk or
b) an
> interesting opinion on which exception handlers I
should be
> investigating?
>

our team uses Error, i'd also be interested in looking at
the talk and
learning about other people's opinions.

cheers,

pedro
-- 
http://pedrofigueiredo.or
g/
bgp is for those who can't keep it static long enough

On Wed, Jul 11, 2007 at 11:51:17AM +0100, Dave Cross wrote:
> We're currently contemplating changing the exception
handling for the  
> project I'm maintaining and Mark's talk would be a good
introduction  
> to the issues we need to consider. Unfortunately, it
doesn't seem to  
> be on the tech talk page on the web site[2].
> 
> So, does anyone have either a) a link to that talk or
b) an  
> interesting opinion on which exception handlers I
should be  
> investigating?

I quite like using: methods always return a true value on
success, and
if they fail, you make a log, and return false yourself.
Requires a very
lightweight instantiator that always passes tho, and you do
have to
occasionally do nasty things like return empty arrayrefs.

It is simple, however.

It's entirely possible, though, I guess, that the project
you're
maintaining is the last large-scale piece of work I wrote
that did
things that way 

-P

Dave Cross wrote:
> So, does anyone have either a) a link to that talk or
b) an interesting
> opinion on which exception handlers I should be
investigating?

The author of Exception::Base has some comments here:

<http://search.cpan.org/~dex
ter/Exception-Base-0.07/lib/Exception/Base.pm#SEE_ALSO>


[Disclaimer: I've not used E::B at all - just saw it on CPAN
Recent a
while back]

-- 
John O'Shea
Wordbank Limited
33 Charlotte Street, bond W1T 1RR
Direct line: +44 (0) 20 7903 8829
Fax: +44 (0) 20 7903 8888
<http://www.wordbank.com/
>

* Dave Cross (davedave.org.uk) [070711 10:51]:
> So, does anyone have either a) a link to that talk or
b) an  
> interesting opinion on which exception handlers I
should be  
> investigating?

Somewhere inbetween the pale die/warn, and the full OO
exceptions,
there is the new Log::Report distribution.  It provides more
levels
of errors than just die, and of course implements
"try".  Besides,
it is integrated with an (optional) translation network,
such that
your web-user can have a message in Chinese, where the
syslog has
the report in English.

Can you wait to YAPC::EU, or do you like the slides
beforehand   
-- 
Regards,
               MarkOv

------------------------------------------------------------
------------
       Mark Overmeer MSc                               
MARKOV Solutions
       MarkOvermeer.net                          solutionsovermeer.net
http://Mark.Overmeer.net
                  http://solutions.overme
er.net

Pete Sergeant wrote:
> I quite like using: methods always return a true value
on success, and
> if they fail, you make a log, and return false
yourself. Requires a very
> lightweight instantiator that always passes tho, and
you do have to
> occasionally do nasty things like return empty
arrayrefs.
> 
> It is simple, however.

Uh oh. Here we go 

Can I just say semi-predicate and then run away?

-- 
Andy Armstrong, Hexten

Quoting Mark Overmeer <markovermeer.net>:

> Somewhere inbetween the pale die/warn, and the full OO
exceptions,
> there is the new Log::Report distribution.  It provides
more levels
> of errors than just die, and of course implements
"try".  Besides,
> it is integrated with an (optional) translation
network, such that
> your web-user can have a message in Chinese, where the
syslog has
> the report in English.

Sounds interesting. Tho' I'm not talking about web-based
applications  
- is that a problem?

> Can you wait to YAPC::EU, or do you like the slides
beforehand 

I won't actually be at YAPC::EU[1], but I won't get to this
work until  
after then anyway, so I'll wait and read your slides later.

Cheers,

Dave...

[1] Damn inconvenient holiday in New Zealand. On balance I
think I've  
got the better deal.

-- 
site: http://dave.org.uk/
blog: http://blog.dave.org.uk/

On 7/11/07, Dave Cross <davedave.org.uk> wrote:
>
> (I apologise in advance for the on-topic[1] nature of
this mail)
>
> A couple of years ago, I can remember sitting in
Fotango's office
> listening to Mark Fowler give an interesting talk about
the various
> Perl exception handling modules. As I recall it ended
by saying they
> all had their faults which is why he had written
another one.
>
> We're currently contemplating changing the exception
handling for the
> project I'm maintaining and Mark's talk would be a good
introduction
> to the issues we need to consider. Unfortunately, it
doesn't seem to
> be on the tech talk page on the web site[2].
>
> So, does anyone have either a) a link to that talk or
b) an
> interesting opinion on which exception handlers I
should be
> investigating?
>
> Cheers,
>
> Dave...
>
> [1] Or is that "off-topic"? I can never
remember.
> [2] http://bond.pm.org/tec
h_talks/
>
> --
> site: http://dave.org.uk/
> blog: http://blog.dave.org.uk/

>
>

Hello Dave,

If you're using a web application, I recommend CGI::Carp,
because you
can write an personalized routine to handle application
errors. I my
case, when my scripts return an error (like an die, or any
other
fail), instead my users view "Internal Server
Error" (from Apache),
they see my error routine build with Carp and CGI ... It's
very
interesting.

best regards,

-- 
 | --
 | Otávio Fernandes <otaviof at gmail dot com>
 | FreeBSD 6.2 Release && GNU/Linux User: 283.396
 | http://otaviof.googlep
ages.com
 | --

* Dave Cross (davedave.org.uk) [070711 12:51]:
> Quoting Mark Overmeer <markovermeer.net>:
>> Somewhere inbetween the pale die/warn, and the full
OO exceptions,
>> there is the new Log::Report distribution.

> Sounds interesting. Tho' I'm not talking about
web-based applications  
> - is that a problem?

That was just as example.

> >Can you wait to YAPC::EU, or do you like the slides
beforehand 

> I won't actually be at YAPC::EU[1], but I won't get to
this work until  
> after then anyway, so I'll wait and read your slides
later.

I'll send you the slides of my Amsterdam.pm talk in private,
after
this e-mail.  The man-page should be clear as well.
-- 
Regards,

               MarkOv

------------------------------------------------------------
------------
       Mark Overmeer MSc                               
MARKOV Solutions
       MarkOvermeer.net                          solutionsovermeer.net
http://Mark.Overmeer.net
                  http://solutions.overme
er.net

On 7/11/07, Otávio Fernandes <otaviofgmail.com> wrote:
> On 7/11/07, Dave Cross <davedave.org.uk> wrote:
> >
> > (I apologise in advance for the on-topic[1] nature
of this mail)
> >
> > A couple of years ago, I can remember sitting in
Fotango's office
> > listening to Mark Fowler give an interesting talk
about the various
> > Perl exception handling modules. As I recall it
ended by saying they
> > all had their faults which is why he had written
another one.
> >
> > We're currently contemplating changing the
exception handling for the
> > project I'm maintaining and Mark's talk would be a
good introduction
> > to the issues we need to consider. Unfortunately,
it doesn't seem to
> > be on the tech talk page on the web site[2].
> >
> > So, does anyone have either a) a link to that talk
or b) an
> > interesting opinion on which exception handlers I
should be
> > investigating?
> >
> > Cheers,
> >
> > Dave...
> >
> > [1] Or is that "off-topic"? I can never
remember.
> > [2] http://bond.pm.org/tec
h_talks/
> >
> > --
> > site: http://dave.org.uk/
> > blog: http://blog.dave.org.uk/

> >
> >
>
> Hello Dave,
>
> If you're using a web application, I recommend
CGI::Carp, because you
> can write an personalized routine to handle application
errors. I my
> case, when my scripts return an error (like an die, or
any other
> fail), instead my users view "Internal Server
Error" (from Apache),
> they see my error routine build with Carp and CGI ...
It's very
> interesting.
>
> best regards,
>
> --
>  | --
>  | Otávio Fernandes <otaviof at gmail dot com>
>  | FreeBSD 6.2 Release && GNU/Linux User:
283.396
>  | http://otaviof.googlep
ages.com
>  | --
>

http://search.cpan.org/~lds/CGI.
pm-3.29/CGI/Carp.pm#Changing_the_default_message