Re: How should a container class "know" its contained objects?
- From: "Daniel T." <daniel_t@xxxxxxxxxxxxx>
- Date: Wed, 16 Jan 2008 10:13:37 -0800 (PST)
On Jan 16, 11:13 am, Veloz <michaelve...@xxxxxxxxx> wrote:
No you don't. You have to honor and enforce the behavioral relationships
dictated by the domain. That's what OO is about.
Wow, that really got me thinking. .. I suspect this line of thought
is related to the quote
you sent from Martin, in which he talks about not designing the
solution by mimicking the
domain entities and their relationships, but rather by.. I guess..
finding the "essence" of the
responsibilities that have to be provided for in the domain (aka the
behaviors) and then modeling
those.
Yes?
Right. Unless, of course, you are writing a database application,
where you are basically taking data, transforming it (in some possibly
very complex way,) then presenting it to the user.
.
- Follow-Ups:
- References:
- How should a container class "know" its contained objects?
- From: Veloz
- Re: How should a container class "know" its contained objects?
- From: Veloz
- Re: How should a container class "know" its contained objects?
- From: Daniel T.
- Re: How should a container class "know" its contained objects?
- From: Veloz
- Re: How should a container class "know" its contained objects?
- From: Daniel T.
- Re: How should a container class "know" its contained objects?
- From: Veloz
- How should a container class "know" its contained objects?
- Prev by Date: Re: which of these OO books for 1st reading ?
- Next by Date: Re: Business objects, subset of collection
- Previous by thread: Re: How should a container class "know" its contained objects?
- Next by thread: Re: How should a container class "know" its contained objects?
- Index(es):
Relevant Pages
|