Re: Exception Handling - Good Practice
- From: rowe_newsgroups <rowe_email@xxxxxxxxx>
- Date: Tue, 04 Sep 2007 06:44:19 -0700
On Sep 4, 4:12 am, "CJM" <cjmnew...@xxxxxxxxxxxxxxxx> wrote:
Thanks for the answers guys.
It's worth pointing out that in this particular scenario, the application is
reading email addresses from a DB so there is no opportunity for interaction
with a user. I'm just going to ignore an address if it isn't valid. I do
have some Regex code to parse email addresses, so I'm going to handle it
in-code; if the email is malformed, I'll tell it to just move on to the next
one...
CJM
My opinion would then be to wrap the Regex checks in a seperate bool
function. Then after pulling the possible addresses from the DB you
could use a very simple if...then block to filter the addresses.
Thanks,
Seth Rowe
.
- Follow-Ups:
- Re: Exception Handling - Good Practice
- From: CJM
- Re: Exception Handling - Good Practice
- References:
- Exception Handling - Good Practice
- From: CJM
- Re: Exception Handling - Good Practice
- From: CJM
- Exception Handling - Good Practice
- Prev by Date: Re: IIS
- Next by Date: RE: Visual Basic 2005.Net TableAdapters
- Previous by thread: Re: Exception Handling - Good Practice
- Next by thread: Re: Exception Handling - Good Practice
- Index(es):
Relevant Pages
|