From fcc200d6d8a6a4dd55a81f3ef3ff2608bbcf144d Mon Sep 17 00:00:00 2001 From: jfiat Date: Tue, 9 Feb 2010 12:15:00 +0000 Subject: [PATCH] Author:jfiat Date:2010-02-09T12:15:00.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@445 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../current/method/eiffel-tutorial-et/et-instructions.wiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/current/method/eiffel-tutorial-et/et-instructions.wiki b/documentation/current/method/eiffel-tutorial-et/et-instructions.wiki index f907ba49..ee95ce59 100644 --- a/documentation/current/method/eiffel-tutorial-et/et-instructions.wiki +++ b/documentation/current/method/eiffel-tutorial-et/et-instructions.wiki @@ -127,7 +127,7 @@ The ''loop body'' part: ''loop body part.'' -The loop body part contains the sequence of instructions to be executed during each iteration. In the example, that includes printing the current list item and then advancing the cursor. At some point, the cursor will pass the last item in the list, causing the exit condition to become true and stop the loop's execution. So, at the risk of stating the obvious, the key to loops that always complete is to ensure that there is something in the loop body that is guaranteed always to cause the exit condition eventually to become true. Loop correctness will discussed in more detail later. +The loop body part contains the sequence of instructions to be executed during each iteration. In the example, that includes printing the current list item and then advancing the cursor. At some point, the cursor will pass the last item in the list, causing the exit condition to become true and stop the loop's execution. So, at the risk of stating the obvious, the key to loops that always complete is to ensure that there is something in the loop body that is guaranteed always to cause the exit condition eventually to become true. Loop correctness will discussed in more detail [[#Loop invariants and variants|later]]. And finally, there's the ''End'' part: