Revision as of 15:20, 22 February 2006 edit Joheriks (talk \| contribs) 5 edits No edit summary ← Previous edit		Revision as of 09:23, 23 February 2006 edit undo Joheriks (talk \| contribs) 5 edits m Some interlinks Next edit →
Line 3: Writing invariants before program statements has been considered before in a number of different forms by, e.g, M.H. van Emden, [[Edsger Dijkstra\|E.W. Dijkstra]], J.C. Reynolds and [[Ralph-Johan Back\|R-J Back]]. Most existing programming languages are not ideal for invariants-first programming, since the main organizing structures in algorithmic code are control flow blocks such as [[For loop\|<tt>for</tt> loops]], [[While loop\|<tt>while</tt> loops]] and [[If statement\|<tt>if</tt> statements]]. This forces the programmer to make decisions about control flow before writing the invariants, which should be avoided. Furthermore, most programming languages do not have good support for writing specifications and invariants, since they lack quantifier operators and one can typically not express higher order properties such as permutation of arrays well. == Links ==

Invariant-based programming: Difference between revisions