Beginning in DDMS 4.0.1, a ddms:type element can contain child text. The intent of this text is to provide further context when the ddms:type element references an IC activity.
{@table.footer}{@table.header Nested Elements}None. {@table.footer}{@table.header Attributes}{@child.info ddms:qualifier|1|11111}{@child.info ddms:value|1|11111}{@table.footer}{@table.header Validation Rules}{@ddms.rule The qualified name of this element must be correct.|Error|11111}{@ddms.rule ddms:qualifier must exist, and must be a valid URI.|Error|11111}{@ddms.rule ddms:value must exist.|Error|11111}{@table.footer} @author Brian Uri! @since 0.9.bidentifier ::= {@link SimpleIdentifier simpleIdentifier}| {@link PrefixedIdentifier prefixedIdentifier}@coverage dart.engine.ast
Implementation for a message selector language Identifier node.
e.g.$variableName - variableName is the identifier, foo() - foo is the identifier, $myClass->fun() - myClass and fun are identifiers
An identifier instance is very similar to a String. The difference is that identifier can't be instanciated directly, instead they are looked up in a hash table. This means that identifiers with the same name map to the same identifier object. This makes comparisons of identifiers much faster.
A lot of identifiers are qualified, that is they have '.'s in them. Each qualified identifier is chopped up into the qualifier and the name. The qualifier is cached in the value field.
Unqualified identifiers can have a type. This type is an integer that can be used by a scanner as a token value. This value has to be set using the setType method.
WARNING: The contents of this source file are not part of any supported API. Code that depends on them does so at its own risk: they are subject to change or removal without notice. @author Arthur van Hoff
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|