What are the differences pre condition ,post condition and invariant in computer terminology [closed]

Question

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.

Closed 8 years ago.

I am reading the book Java Concurrency in Practice and getting a little bit confused with these terms:

1. Pre condition
2. Post condition
3. Invariants

Can someone please explain me them (with an example, if it's possible)?

Answer 1

You'll have a lot of problems writing Java, especially multi-threaded code, if you can't understand these simple ideas:

1. Pre-conditions are the things that must be true before a method is called. The method tells clients "this is what I expect from you".
2. Post-conditions are the things that must be true after the method is complete. The method tells clients "this is what I promise to do for you".
3. Invariants are the things that are always true and won't change. The method tells clients "if this was true before you called me, I promise it'll still be true when I'm done".

They're all part of an idea called "programming by contract". It was invented by a guy named C.A.R. Hoare. Bertrand Meyer built an object oriented language called Eiffel around it. No one uses it much, but he had a day in the sun because of it.

Eiffel isn't very popular. There are over four million questions on SO as I write this, but only 32 of them are tagged "eiffel".

Update: There were 11,966,392 question on SO on 29-Jun-2016. Only 92 of them were tagged "eiffel". The percentage of Eiffel questions is staying roughly constant at ~0.00077%.

I stand corrected - thank you, flamingpenguin. I've updated my answer.