[Home] [Groups] - Message: [Prev in Group] [Next in Group]
15853: RE: [MUD-Dev] Object Models
[Full Header] [Plain Text]
From: "John Buehler" <johnbue@msn.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Tue, 28 Nov 2000 14:56:46 -0800
References: [1]
Organization: Kanga.Nu
> Miroslav Silovic
> The Right solution to this is to use a slight variant of the
> covariance principle in OO language design. Components (or libraries
> or modules or whatever you choose to call them) should guarantee as
> tight a contract as possible, while modules that use these components
> should impose as loose contracts as possible. In other words,
> components should be specced in a way that says 'no less than this'
> while the clients should have requirements that end with 'and nothing
> more than this'. This way, even if you are forced to change one side
> of a contract, there's a good chance that you won't hit the wall on
> the other side.
Agreed. No point in requiring what you don't need. If all you need to USE
is a fastener then go with that.
JB
_______________________________________________
MUD-Dev mailing list
MUD-Dev@kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev