Searched refs:qualified (Results 1 – 15 of 15) sorted by relevance
624 val qualified = in <lambda>() constant627 val qualified = cls.fullyQualifiedDocumentation(original) in <lambda>() constant628 if (original != qualified) { in <lambda>()629 qualified.substring(if (qualified[3] == ' ') 4 else 3, qualified.length - 2) in <lambda>()637 item.appendDocumentation(qualified, section) // 2: @ and space after tag in <lambda>()
32 // Method identifier: fully qualified module + method names
90 (Notice how the annotations are not using fully qualified name; that's discussed96 The annotations should be sorted alphabetically by fully qualified name.422 classes. The classes are listed by fully qualified name, but in v1 it was sorted423 by simple name. In the v2 format, we sort by fully qualified name instead.445 That begs the question: which fully qualified name should we put in the
22 REM and set up progdir to be the fully-qualified pathname of its directory.
140 // The fully-qualified name of the exception class associated with the error.
152 // The fully-qualified name of the exception class associated with the error.
132 --ks-provider-class Fully-qualified class name of the JCA Provider from which191 --provider-class Fully-qualified class name of the JCA Provider.
243 --ks-provider-class Fully-qualified class name of the JCA Provider from which267 --provider-class Fully-qualified class name of the JCA Provider.
126 --ks-provider-class Fully-qualified class name of the JCA Provider from which
128 tradefed.sh run host -n --class <fully.qualified.ClassName>
165 # supports qualified module names, as well as Unix pattern matching.170 # with qualified names.
3920 fun `v3 format for qualified references in types`() { in v3 format for qualified references in types()
272 fun `Test annotations on qualified class type`() { in <lambda>()
157 // starts with a '.', it is fully-qualified. Otherwise, C++-like scoping