Author:jfiat

Date:2012-07-31T10:24:51.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1126 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2012-08-13 01:52:50 +00:00
parent 5535b2f1ce
commit b324762992
2 changed files with 2 additions and 2 deletions

View File

@@ -18,7 +18,7 @@ If the expression has an error, or if the evaluation raised an exception, you ca
{{caution|Eiffel ''agents'' (for example: <code>agent my_function</code>) are not supported is not supported. }} {{caution|Eiffel ''agents'' (for example: <code>agent my_function</code>) are not supported is not supported. }}
{{caution|The evaluation ignores void-safety checking, a side effect is that expression "{FOO}" is interpreted as "{detachable FOO}" even if your application is void-safe. Thus keep this in mind when your expression implies TYPE objects. }} {{caution|The evaluation ignores void-safety checking, a side effect is that expression <code>{FOO}</code> is interpreted as <code>{detachable FOO}</code> even if your application is void-safe. Thus keep this in mind when your expression implies <code>TYPE</code> objects. }}
{{caution|Currently, for classic Eiffel systems, evaluating <code>Precursor</code> will result the current feature's result (not the precursor). }} {{caution|Currently, for classic Eiffel systems, evaluating <code>Precursor</code> will result the current feature's result (not the precursor). }}

View File

@@ -171,7 +171,7 @@ And finally, there's the ''End'' part:
====A closer look at the ''iteration'' form==== ====A closer look at the ''iteration'' form====
Now let's examine the iteration form used in ''Loop example 2.'' Now let's examine the iteration form (sometimes called the "across syntax") used in ''Loop example 2.''
The example begins with an iteration part: The example begins with an iteration part: