mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-06 14:52:03 +01:00
Merged significant changes from trunk into 19.12 and 20.05
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@2246 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -1,3 +1,5 @@
|
||||
[[Property:modification_date|Tue, 23 Jun 2020 07:13:21 GMT]]
|
||||
[[Property:publication_date|Tue, 23 Jun 2020 07:13:21 GMT]]
|
||||
[[Property:title|Expression evaluation]]
|
||||
[[Property:weight|-10]]
|
||||
[[Property:uuid|e55442ac-7861-1995-d315-baeed6c49223]]
|
||||
@@ -16,7 +18,7 @@ If the expression has an error, or if the evaluation raised an exception, you ca
|
||||
|
||||
{{caution|During the evaluation of an expression, all features that are necessary to obtain the result are called. Therefore, you should avoid calling queries that have side-effects, since doing so may alter the program execution. The Eiffel methodology recommends against creating queries with side-effects for other important reasons, as well. }}
|
||||
|
||||
{{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>) is not supported. }}
|
||||
|
||||
{{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. }}
|
||||
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
[[Property:modification_date|Thu, 25 Jun 2020 07:27:10 GMT]]
|
||||
[[Property:publication_date|Thu, 25 Jun 2020 07:27:10 GMT]]
|
||||
[[Property:title|Criterion References]]
|
||||
[[Property:weight|12]]
|
||||
[[Property:uuid|52790486-55e8-86dc-67d7-5530d1b342a3]]
|
||||
@@ -48,12 +50,12 @@
|
||||
'''path_in'''<br/>
|
||||
'''Syntax:''' path_in "path"<br/>
|
||||
'''Applicable on:''' Class<br/>
|
||||
'''Remark:''' This criterion will evaluate to True if path (related to the class's written in group) of the class candidate is "path" or its subdirectory. "path" is in Unix format, i.e., different sections are separated by a "/". On Windows, path matching is case-sensitive, on other platforms, it's case-sensitive.
|
||||
'''Remark:''' This criterion will evaluate to True if path (related to the class's written in group) of the class candidate is "path" or its subdirectory. "path" is in Unix format, i.e., different sections are separated by a "/". On Windows, path matching is case-insensitive, on other platforms, it's case-sensitive.
|
||||
|
||||
'''path_is'''<br/>
|
||||
'''Syntax:''' path_is "path"<br/>
|
||||
'''Applicable on:''' Class<br/>
|
||||
'''Remark:''' This criterion will evaluate to True if path (related to the class's written in group) of the class candidate is "path". "path" is in Unix format, i.e., different sections are separated by a "/". On Windows, path matching is case-sensitive, on other platforms, it's case-sensitive.
|
||||
'''Remark:''' This criterion will evaluate to True if path (related to the class's written in group) of the class candidate is "path". "path" is in Unix format, i.e., different sections are separated by a "/". On Windows, path matching is case-insensitive, on other platforms, it's case-sensitive.
|
||||
|
||||
==Relation Criterion==
|
||||
|
||||
|
||||
Reference in New Issue
Block a user