This is a highly general thought, but let’s use C# in this example.
Given that
- I have a disposable class
Foo, i.e., it implementsIDisposable. Foohas a boolean flagdisposedthat is false untilDisposeis called, after which it’s true.- All public methods of
FoothrowsObjectDisposedExceptionifdisposedis true when they are called.
Does this statement
Any method of
Foo, exceptDispose, will throw anObjectDisposedExceptionwhen called on an instance ofFoothat has been disposed.
describe an invariant of Foo?
No.
This is a set of rules common to all the methods of the class. Invariants are not rules for methods.
Design by Contract comprises defining the following parts of a contract:
What you are describing are method postconditions. They belong to the contract of each function (which is of course part of the contract of the class), but not to the class invariant.