Searched refs:lexical (Results 1 – 25 of 145) sorted by relevance
123456
| /external/javaparser/doc/ |
| D | component_diagram.puml | 5 [AST] <-- [lexical preserving printer]
7 [concrete syntax model] <-- [lexical preserving printer]
8 events <-- [lexical preserving printer]
|
| /external/rust/crates/nom/ |
| D | Cargo.toml.orig | 32 default = ["std", "lexical"]
35 lexical = ["lexical-core"]
49 [dependencies.lexical-core]
62 features = [ "alloc", "std", "regexp", "regexp_macros", "lexical"]
|
| D | Cargo.toml | 29 features = ["alloc", "std", "regexp", "regexp_macros", "lexical"]
143 [dependencies.lexical-core]
167 default = ["std", "lexical"]
168 lexical = ["lexical-core"]
|
| /external/python/cpython2/Doc/reference/ |
| D | introduction.rst | 12 than formal specifications for everything except syntax and lexical analysis.
96 The descriptions of lexical analysis and syntax use a modified BNF grammar
106 adhered to for the names defined in lexical and grammar rules in this document.)
121 single: lexical definitions
124 In lexical definitions (as the example above), two more conventions are used:
132 between the meaning of lexical and syntactic definitions: a lexical definition
134 definition operates on the stream of tokens generated by the lexical analysis.
135 All uses of BNF in the next chapter ("Lexical Analysis") are lexical
|
| D | lexical_analysis.rst | 9 single: lexical analysis
14 *tokens*, generated by the *lexical analyzer*. This chapter describes how the
15 lexical analyzer breaks a file into tokens.
129 encoding is used for all lexical analysis, in particular to find the end of a
281 error is found by the lexical analyzer --- the indentation of ``return r`` does
318 Identifiers (also referred to as *names*) are described by the following lexical
422 String literals are described by the following lexical definitions:
633 Integer and long integer literals are described by the following lexical
670 Floating point literals are described by the following lexical definitions:
698 Imaginary literals are described by the following lexical definitions:
[all …]
|
| /external/python/cpython3/Doc/reference/ |
| D | introduction.rst | 12 than formal specifications for everything except syntax and lexical analysis.
93 The descriptions of lexical analysis and syntax use a modified BNF grammar
103 adhered to for the names defined in lexical and grammar rules in this document.)
117 .. index:: lexical definitions, ASCII
119 In lexical definitions (as the example above), two more conventions are used:
127 between the meaning of lexical and syntactic definitions: a lexical definition
129 definition operates on the stream of tokens generated by the lexical analysis.
130 All uses of BNF in the next chapter ("Lexical Analysis") are lexical
|
| D | lexical_analysis.rst | 8 .. index:: lexical analysis, parser, token
11 *tokens*, generated by the *lexical analyzer*. This chapter describes how the
12 lexical analyzer breaks a file into tokens.
105 encoding is used for all lexical analysis, including string literals, comments
246 error is found by the lexical analyzer --- the indentation of ``return r`` does
281 Identifiers (also referred to as *names*) are described by the following lexical
413 String literals are described by the following lexical definitions:
821 Integer literals are described by the following lexical definitions:
865 Floating point literals are described by the following lexical definitions:
895 Imaginary literals are described by the following lexical definitions:
[all …]
|
| /external/clang/test/Index/ |
| D | index-decls.m | 67 …kind: objc-instance-method | name: prop | {{.*}} | loc: 11:13 | {{.*}} | lexical-container: [I:10:…
68 …: objc-instance-method | name: setProp: | {{.*}} | loc: 11:13 | {{.*}} | lexical-container: [I:10:…
|
| /external/llvm-project/clang/test/Index/ |
| D | index-decls.m | 67 …kind: objc-instance-method | name: prop | {{.*}} | loc: 11:13 | {{.*}} | lexical-container: [I:10:…
68 …: objc-instance-method | name: setProp: | {{.*}} | loc: 11:13 | {{.*}} | lexical-container: [I:10:…
|
| /external/javaparser/javaparser-core-testing/src/test/resources/com/github/javaparser/lexical_preservation_samples/ |
| D | ASimpleClassWithMoreFormatting_step1.java.txt | 5 * A class with some uncommon formatting, to check the lexical preservation
|
| D | ASimpleClassWithMoreFormatting.java.txt | 5 * A class with some uncommon formatting, to check the lexical preservation
|
| D | ASimpleClassWithMoreFormatting_step2.java.txt | 5 * A class with some uncommon formatting, to check the lexical preservation
|
| D | ASimpleClassWithMoreFormatting_step3.java.txt | 5 * A class with some uncommon formatting, to check the lexical preservation
|
| D | ASimpleClassWithMoreFormatting_step4.java.txt | 5 * A class with some uncommon formatting, to check the lexical preservation
|
| /external/llvm-project/clang/test/Modules/ |
| D | inner-struct-redefines-invisible.m | 8 // Should set lexical context when parsing 'Inner' here, otherwise there's a crash:
|
| /external/python/cpython2/Doc/library/ |
| D | shlex.rst | 1 :mod:`shlex` --- Simple lexical analysis
5 :synopsis: Simple lexical analysis for Unix shell-like languages.
19 The :class:`~shlex.shlex` class makes it easy to write lexical analyzers for
54 A :class:`~shlex.shlex` instance or subclass instance is a lexical analyzer
161 variables which either control lexical analysis or can be used for debugging:
232 string will be recognized as a lexical-level inclusion request similar to the
|
| /external/clang/test/CodeGenObjC/ |
| D | catch-lexical-block.m | 10 // We should have 3 lexical blocks here at the moment, including one
|
| /external/llvm-project/clang/test/CodeGenObjC/ |
| D | catch-lexical-block.m | 10 // We should have 3 lexical blocks here at the moment, including one
|
| /external/llvm-project/llvm/test/DebugInfo/X86/ |
| D | asan_debug_info.ll | 23 ; intersect with the ranges of the parent lexical scope. But recreating that
24 ; exactly requires playing tricks to get LiveDebugValue's lexical dominance
|
| D | rnglists_base_attr.ll | 22 ; for the variable b, creates a gap in the code range for the nested lexical
39 ; Make sure we see 2 ranges in the lexical block DIE.
|
| D | trim-var-locs.mir | 72 ; (2) Check that a variable location range found outside lexical block is
80 ; (3) Check that a variable location range which overlaps the entire lexical
|
| /external/llvm/test/Transforms/LoopLoadElim/ |
| D | backward.ll | 3 ; Simple st->ld forwarding derived from a lexical backward dep.
|
| /external/python/cpython3/Doc/library/ |
| D | shlex.rst | 1 :mod:`shlex` --- Simple lexical analysis
5 :synopsis: Simple lexical analysis for Unix shell-like languages.
16 The :class:`~shlex.shlex` class makes it easy to write lexical analyzers for
98 A :class:`~shlex.shlex` instance or subclass instance is a lexical analyzer
214 variables which either control lexical analysis or can be used for debugging:
292 string will be recognized as a lexical-level inclusion request similar to the
|
| /external/llvm-project/llvm/test/Transforms/LoopLoadElim/ |
| D | backward.ll | 4 ; Simple st->ld forwarding derived from a lexical backward dep.
|
| /external/python/setuptools/docs/ |
| D | development.txt | 12 dependencies, nor does it contain detailed lexical syntax for most
|
123456