Searched refs:lexical (Results 1 – 25 of 44) sorted by relevance
12
| /external/clang/test/Index/ |
| D | index-decls.m | 61 …kind: objc-instance-method | name: prop | {{.*}} | loc: 11:13 | {{.*}} | lexical-container: [I:10:…
62 …: objc-instance-method | name: setProp: | {{.*}} | loc: 11:13 | {{.*}} | lexical-container: [I:10:…
|
| /external/clang/test/CodeGenObjC/ |
| D | catch-lexical-block.m | 10 // We should have 3 lexical blocks here at the moment, including one
|
| /external/antlr/antlr-3.4/runtime/ObjC/ |
| D | README | 1 ANTLR version 3 supports target language generation for the lexical
|
| /external/llvm/test/DebugInfo/COFF/ |
| D | tail-call-without-lexical-scopes.ll | 15 ; The bar function happens to have no lexical scopes, yet it has one instruction
|
| /external/llvm/test/Transforms/AddDiscriminators/ |
| D | no-discriminators.ll | 13 ; new lexical scope.
|
| /external/antlr/antlr-3.4/gunit/ |
| D | CHANGES.txt | 78 * added new functionality of testing lexical rules
|
| /external/tagsoup/ |
| D | CHANGES | 44 Removed lexical handler calls to startCDATA/endCDATA from CDATA element handling
45 Added lexical handler calls to startCDATA/endCDATA from CDATA section handling
85 --lexical switch now outputs DOCTYPE if there is one
|
| /external/llvm/docs/TableGen/ |
| D | LangRef.rst | 24 The lexical and syntax notation used here is intended to imitate
25 `Python's`_. In particular, for lexical definitions, the productions
|
| /external/smali/smali/src/test/antlr3/org/jf/smali/ |
| D | expectedTokensTestGrammar.g | 2 * The string related lexical rules are derived from rules from the
|
| /external/icu/icu4c/source/tools/toolutil/ |
| D | ucm.c | 126 UBool lexical) { in compareBytes() argument
138 if(lexical) { in compareBytes()
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2001-02-06-TypeNotationDebateResp4.txt | 31 I would argue that because the lexical structure of the language is self
|
| /external/antlr/antlr-3.4/runtime/Ruby/ |
| D | README.txt | 46 * parsing lexical output and responding with arbitrary actions
|
| /external/clang/docs/ |
| D | BlockLanguageSpec.rst | 148 The compound statement body establishes a new lexical scope within
275 references to instance variables are also imported into the lexical
|
| D | PTHInternals.rst | 100 a lexical cache of header files, a single PTH file can be safely used
|
| D | InternalsManual.rst | 1151 *lexical* context, which corresponds to the source-centric view of the
1153 semantics-centric view. The lexical context is accessible via
1165 Here, the semantic and lexical contexts of ``X::f`` are the ``DeclContext``
1173 This definition of "``f``" has different lexical and semantic contexts. The
1174 lexical context corresponds to the declaration context in which the actual
1228 same set of requirements: declarations are declared within a particular lexical
1234 lexical context of the declaration (e.g., an enumerator) will be the
|
| /external/lldb/scripts/ |
| D | lldb.swig | 29 o SBBlock: Represents a lexical block. SBFunction contains SBBlock(s).
|
| /external/llvm/docs/tutorial/ |
| D | LangImpl8.rst | 299 current "lexical location" to the assorted line and column for the beginning
380 // Pop off the lexical block for the function since we added it
|
| /external/parameter-framework/tools/xmlGenerator/ |
| D | README.md | 166 When setting an enum parameter value, use its lexical space, not its numerical
|
| /external/bison/doc/ |
| D | bison.texi | 157 * Rpcalc Lexer:: The lexical analyzer.
173 * Ltcalc Lexer:: The lexical analyzer.
1260 @cindex lexical analyzer, purpose
1277 The tokens come from a function called the @dfn{lexical analyzer} that
1279 parser calls the lexical analyzer each time it wants a new token. It
1281 may reflect this). Typically the lexical analyzer makes the tokens by
1288 additional functions. One is the lexical analyzer. Another is an
1298 functions such as the lexical analyzer function @code{yylex}, the
1334 Write a lexical analyzer to process input and pass tokens to the parser.
1335 The lexical analyzer may be written by hand in C (@pxref{Lexical, ,The
[all …]
|
| D | bison.info | 120 * Rpcalc Lexer:: The lexical analyzer.
136 * Ltcalc Lexer:: The lexical analyzer.
1849 The tokens come from a function called the "lexical analyzer" that
1851 parser calls the lexical analyzer each time it wants a new token. It
1853 may reflect this). Typically the lexical analyzer makes the tokens by
1860 functions. One is the lexical analyzer. Another is an error-reporting
1869 as the lexical analyzer function `yylex', the error reporting function
1901 2. Write a lexical analyzer to process input and pass tokens to the
1902 parser. The lexical analyzer may be written by hand in C (*note
1947 You need to declare the lexical analyzer `yylex' and the error printer
[all …]
|
| /external/antlr/antlr-3.4/runtime/ActionScript/project/src/org/antlr/runtime/ |
| D | Lexer.as | 140 * outermost lexical rule. The token object should point into the
|
| /external/antlr/antlr-3.4/runtime/JavaScript/tests/functional/ |
| D | rhino-python.extensions | 32 This is an interesting lexical problem because multiple DEDENT
|
| D | Python.g | 49 * The lexical rules for python are particularly nasty and it took me
|
| /external/antlr/antlr-3.4/runtime/ObjC/Framework/ |
| D | ANTLRLexer.m | 194 * outermost lexical rule. The token object should point into the
|
| /external/mesa3d/src/glsl/ |
| D | glsl_parser.yy | 487 // Grammar Note: Constructors look like functions, but lexical
542 // Grammar Note: Constructors look like methods, but lexical
|
12