Re: Tasty exceptions
- From: "Nick Hodges (Borland/DevCo)" <nickhodges@xxxxxxxxx>
- Date: 30 Jun 2006 12:08:02 -0700
Michael C. wrote:
A good programmer would know that there is an error by checking the
return value or the function. ( Perhaps you didn't see the result :=
false statement at beginning of the function. )
Michael --
A good programmer never lets errors go unreported, especially out of
memory errors or I/O errors.
You can continue to program like that if you want -- it's totally up to
you. But I'd never let code like that get past a code review. But
that's just me.
--
Nick Hodges
Delphi/C# Product Manager - Borland/DevCo
Read my Blog -- http://blogs.borland.com/nickhodges
.
- 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: Tasty exceptions
- Previous by thread: Re: Tasty exceptions
- Next by thread: Re: Tasty exceptions
- Index(es):
Relevant Pages
|
|