[MUD-Dev] Object Models

[John Buehler]

> 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 at kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev