Re: Tasty exceptions
- From: "Roddy Pratt" <roddy at spam fritter dot com>
- Date: Fri, 30 Jun 2006 19:59:54 +0100
"Michael C." <Michael@xxxxxxxxxx> wrote in message
news:44a56e87$1@xxxxxxxxxxxxxxxxxxxxxxxxx
A good programmer would know that there is an error by checking the return
value or the function.
A *perfect* programmer would always remember to do that. But a more
pragmatic approach is to realise that by having every function return an
error code - which needs checking and/or passing on up the call stack - your
code becomes an unreadable (and unmaintainable) accident waiting to happen.
I find it strange thate we're even having this discussion in a Delphi
newsgroup: It was Delphi that really introduced me to exceptions, and the
VCL which taught me HOW and WHY to use them...
- Roddy
.
- Follow-Ups:
- Re: Tasty exceptions
- From: Jim Cooper
- Re: Tasty exceptions
- References:
- Tasty exceptions
- From: Blackbird Crow Raven
- Re: Tasty exceptions
- From: Nick Hodges (Borland/DevCo)
- Re: Tasty exceptions
- From: GrandmasterB
- Re: Tasty exceptions
- From: Nick Hodges (Borland/DevCo)
- Re: Tasty exceptions
- From: Michael C.
- Re: Tasty exceptions
- From: Nick Hodges (Borland/DevCo)
- Re: Tasty exceptions
- From: Michael C.
- Re: Tasty exceptions
- From: Nick Hodges (Borland/DevCo)
- Re: Tasty exceptions
- From: Michael C.
- Tasty exceptions
- Prev by Date: Re: Captain Jake's Top Ten List of what I'd like to see in the nextversionofDelphi
- Next by Date: Re: Captain Jake's Top Ten List of what I'd like to see in the nextversionofDelphi
- Previous by thread: Re: Tasty exceptions
- Next by thread: Re: Tasty exceptions
- Index(es):
Relevant Pages
|
|