Searched full:considered (Results 1 – 25 of 125) sorted by relevance
12345
18 List with methods full names, which will be considered as verified.22 List of methods, calls to which always be considered as correct (signature checks is turned off for…
8 they are considered an excessive compiler hint.
8 prototype inheritance in the language. This feature is considered not applicable
9 considered redundant because object layout is known at compile time, and
8 runtime prototype inheritance in the language. This feature is considered not
34 …tion statements in namespaces are not supported (single semicolons are considered as empty non-dec…64 …tion statements in namespaces are not supported (single semicolons are considered as empty non-dec…
17 desc: A declared name is considered private if not exported; a private declared name can be used on…
18 … to member classes (§9.1.5) only. Member classes that are not declared inner are considered static.
18 … pertains to member classes only. Member classes that are not declared inner are considered static.
24 …tion statements in namespaces are not supported (single semicolons are considered as empty non-dec…
17 desc: Enum values from different enum types are considered incompatible.
22 name is considered overloaded.
20 …Entity is considered accessible if it belongs to the current scope (see Scopes) and means that its…
20 not override-equivalent, then the methods’ name is considered overloaded.
18 …s inherited from an interface. In such a situation, the member type is considered to be inherited …
18 …ation is inherited from an interface. In such asituation, the field is considered to be inherited …
18 …therwise, all the inherited methods are abstract, and the interface is considered to inherit all t…