Re: catching multiple exceptions
- From: "Michael C" <mike@xxxxxxxxxx>
- Date: Sun, 1 Mar 2009 01:22:23 +1100
"Andy B." <a_borka@xxxxxxxxxxxxx> wrote in message
news:ujrrhiUmJHA.4540@xxxxxxxxxxxxxxxxxxxxxxx
So the address class should just be a carrier of data. Whatever needs to
be validated should be done at the bigger level (since an address can't
exist by itself) it will be part of another class.
No, I think the address class should validate itself. There are several ways
to do it. One way is to accept the values entered no matter what they are
and have seperate properties the gui can test to determine if there are
errors. Then if the user saves they will get an exception. However this
should never happen as the GUI should warn the user their address is invalid
and stop them saving.
Michael
.
- Follow-Ups:
- class validation
- From: Andy B.
- class validation
- References:
- catching multiple exceptions
- From: Andy B.
- Re: catching multiple exceptions
- From: Martin H.
- Re: catching multiple exceptions
- From: Andy B.
- catching multiple exceptions
- Prev by Date: object (class) validation
- Next by Date: Re: using classes vs. modules
- Previous by thread: Re: catching multiple exceptions
- Next by thread: class validation
- Index(es):
Relevant Pages
|
