--- Comment #3 from deadalnix <> 2012-02-26 07:35:07 PST ---
(In reply to comment #2)
> Again, give an example. Your claim is not true.

In Foo, you sated, by contract, that the function must return 0. Any piece of
code using an object of type Foo rely on the fact that this function return 0.
It is in the contract.

As Bar is a subclass of Foo, it has to respect the contract. An object of type
Bar can be passed to any piece of code expecting an object of type Foo. So,
that piece of code cannot rely on that contract anymore.

In your case, the out contract of should be an unittest. You want that
to be true for object of type Foo, but not for object of subtypes. So contract
isn't the right tool for the job.

Bar doesn't respect Foo's contract, so the contract must fail. This is the
expected behavior. If it weren't the case, then it would be a violation of
Liskov substitution principle, because I couldn't pass an object of type Bar to
a piece of code expecting Foo.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to