Comment by layer8

3 years ago

Software-interface contracts generally aren’t (cf. Design by Contract). The parent is correct insofar as the use of the word “contract” is not limited to contracts as defined by law.

3 comments

layer8

Reply
jrm4  3 years ago

Right, I mean, I've heard this use and I think it's kind of silly.

It's like calling a hopefully-completed-circuit in some device an "electric contract" or something like that.

  • layer8  3 years ago

    It’s a contract (mutual agreement) between the client code and the implementation of the interface. The implementation fulfills certain obligations provided the client code fulfills certain other obligations. The interface defines what those obligations are. If the client code fails to meet its obligations, then the implementation of the interface isn’t bound to fulfill its obligations anymore either. The point is to think in terms of two parties, where the developer who is either using or implementing an interface takes on the role of one of the two contractual parties.