At 07:36 PM 6/24/2002 +0200, you wrote:
>Ok, this said, let's move on. I see two different ways of looking for a
>component:
>
> 1) I need something that does this.
>
> 2) I need something that does this, and should work in this context
I dont see any difference between the above two except the number of
contraints they satisfy.
1) Need X that
* satisfies the "does this" constraint (usually type)
2) Need X that
* satisfies the "does this" constraint (usually type)
* satisfies the work in this context constraint
The number of constraints in a dependency is independent of the name you
give to dependency.
>It has been suggested that the working context is just another
>information you pass in the role, so, in our examples, we would have an
>inflation of roles for each screwdriver and each possible screw size or
>size ranges.
Each dependency can have a different name or not - up to writer of consumer
component. I would never create multiple work interfaces to specify
different dependecies.
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
