mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-08 15:52:26 +01:00
Author:halw
Date:2009-01-27T01:57:16.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@171 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -123,14 +123,14 @@ The related concepts of descendants, proper descendants, heirs, indirect heirs f
|
||||
'''Applicable on:''' Class<br/>
|
||||
'''Remarks:''' This criterion evaluates to True if a candidate class is supplier of any of the classes in criterion domain. Directness modifier is boolean modifier, if it's True only direct suppliers are picked, if indirect modifier is set, only indirect suppliers are picked. normally_referenced and syntactically_referenced modifiers are both boolean modifiers, they enable to specify how one class is used by another class. Let's use an example to demonstrate these ideas, for example, in class A, there is a feature foo:<br/>
|
||||
<code>
|
||||
foo is
|
||||
local
|
||||
l_str: STRING
|
||||
l_file: FILE
|
||||
do
|
||||
create l_str.make_empty
|
||||
end
|
||||
</code>
|
||||
foo
|
||||
local
|
||||
l_str: STRING
|
||||
l_file: FILE
|
||||
do
|
||||
create l_str.make_empty
|
||||
end
|
||||
</code>
|
||||
<br/>
|
||||
Then both <eiffel>STRING</eiffel> and <eiffel>FILE</eiffel> are suppliers of class <eiffel>A</eiffel>. <eiffel>STRING</eiffel> is normal supplier because a feature make_empty in <eiffel>STRING</eiffel> is invoked in class <eiffel>A</eiffel>, but <eiffel>FILE</eiffel> is a syntactically referenced supplier because no feature from <eiffel>FILE</eiffel> is called from <eiffel>A</eiffel>. Classes explicitly listed in inherit clause of a class are also considered as syntactically referenced suppliers.
|
||||
Concepts of direct/indirect, normally referenced/syntactically referenced clients follow the same rule expect in the other direction.
|
||||
@@ -202,6 +202,7 @@ only_current_verision modifier is a boolean modifier, if it's True, when the cri
|
||||
'''Syntax:''' is_implementors_of {domain}<br/>
|
||||
'''Applicable on:''' Feature<br/>
|
||||
|
||||
|
||||
'''Remark:''' This criterion will evaluate to True if the candidate feature is an implementer of some features listed in criterion domain.<br/>
|
||||
|
||||
|
||||
|
||||
@@ -38,17 +38,13 @@ The syntax for name_is is:
|
||||
name_is "pattern", matching_strategy, case_sensitive
|
||||
|
||||
The match_strategy modifier decides how criterion text "pattern" is matched, and can choose from one of the following four values:
|
||||
*
|
||||
Identity - Pattern is matched if the text is identical to criterion text
|
||||
* Identity - Pattern is matched if the text is identical to criterion text
|
||||
|
||||
*
|
||||
Containing - Pattern is matched the text contains criterion text
|
||||
* Containing - Pattern is matched the text contains criterion text
|
||||
|
||||
*
|
||||
Wildcard - Pattern is matched if it occurs in criterion text according to wildcard rules
|
||||
* Wildcard - Pattern is matched if it occurs in criterion text according to wildcard rules
|
||||
|
||||
*
|
||||
Regular expression - Pattern is matched if it occurs in criterion text according to regular expression rules
|
||||
* Regular expression - Pattern is matched if it occurs in criterion text according to regular expression rules
|
||||
|
||||
|
||||
The case_sensitive modifier can be True or False, it indicates if pattern matching is case sensitive or not.
|
||||
|
||||
Reference in New Issue
Block a user