/external/apache-xml/src/main/java/org/apache/xml/dtm/ref/ |
IncrementalSAXSource.java | 47 /** Register a SAX-style lexical handler for us to output to
|
/external/bluetooth/glib/glib/ |
gscanner.h | 47 /* GScanner: Flexible lexical scanner for general purpose.
|
/external/dhcpcd/ |
dhcpcd-run-hooks.8 | 130 in a lexical order and then finally
|
dhcpcd-run-hooks.8.in | 130 in a lexical order and then finally
|
/external/icu4c/i18n/ |
bocsu.h | 33 * - lexical order of the identical-level run must be
|
/external/llvm/docs/HistoricalNotes/ |
2001-02-06-TypeNotationDebateResp4.txt | 31 I would argue that because the lexical structure of the language is self
|
/external/srec/srec/Semproc/include/ |
SR_ExpressionParser.h | 185 * @param lexAnalyzer pointer to the lexical analyzer where the parser gets tokens from
|
/external/v8/src/ |
scanner.h | 163 // Scan a single JSON token. The JSON lexical grammar is specified in the
|
/external/webkit/Tools/android/flex-2.5.4a/ |
FlexLexer.h | 3 // FlexLexer.h -- define interfaces for lexical analyzer classes generated
|
/external/webkit/Tools/android/flex-2.5.4a/MISC/MVS/ |
diffs | 170 /* A lexical scanner generated by flex */ 178 /* A lexical scanner generated by flex */ 329 /* A lexical scanner generated by flex */ 337 /* A lexical scanner generated by flex */
|
/libcore/luni/src/main/java/javax/xml/transform/sax/ |
package.html | 38 {@link org.xml.sax.ContentHandler} interface, lexical events such as
|
/libcore/luni/src/main/java/org/w3c/dom/ls/ |
DOMImplementationLS.java | 57 * newly created <code>LSParser</code>. Note that no lexical checking
|
/libcore/luni/src/main/java/org/xml/sax/ext/ |
DeclHandler.java | 30 * <p>If you are using the declaration handler together with a lexical
|
/external/clang/include/clang/AST/ |
DeclBase.h | 155 /// C++ lexical operator lookup looks for these. 184 /// NextDeclInContext - The next declaration within the same lexical 560 /// setDeclContext - Set both the semantic and lexical DeclContext 686 /// These declarations appear in the lexical context of the friending 872 /// getLexicalParent - Returns the containing lexical DeclContext. May be [all...] |
/external/clang/include/clang-c/ |
Index.h | [all...] |
/external/v8/test/mozilla/ |
mozilla.status | 596 ecma_2/Exceptions/lexical-010: FAIL 597 ecma_2/Exceptions/lexical-022: FAIL 601 ecma_2/Exceptions/lexical-011: FAIL 602 ecma_2/Exceptions/lexical-014: FAIL 603 ecma_2/Exceptions/lexical-016: FAIL 604 ecma_2/Exceptions/lexical-021: FAIL
|
/libcore/luni/src/main/java/javax/xml/datatype/ |
XMLGregorianCalendar.java | 78 * will be a valid lexical value in a future version of XML Schema, 155 * <li>conversion between this class and W3C XML Schema 1.0 lexical representation, 701 * <p>Return the lexical representation of <code>this</code> instance. 704 * <i>Lexical Representation</i>".</a></p> 706 * <p>Specific target lexical representation format is determined by [all...] |
/external/clang/docs/ |
BlockLanguageSpec.txt | 80 The compound statement body establishes a new lexical scope within that of its parent. Variables used within the scope of the compound statement are bound to the Block in the normal manner with the exception of those in automatic (stack) storage. Thus one may access functions and global variables as one would expect, as well as static local variables. [testme] 129 Within a Block literal expression within a method definition references to instance variables are also imported into the lexical scope of the compound statement. These variables are implicitly qualified as references from self, and so self is imported as a const copy. The net effect is that instance variables can be mutated.
|
/external/clang/lib/Sema/ |
IdentifierResolver.cpp | 1 //===- IdentifierResolver.cpp - Lexical Scope Name lookup -------*- C++ -*-===// 10 // This file implements the IdentifierResolver class, which is used for lexical
|
/external/valgrind/main/coregrind/m_debuginfo/ |
readstabs.c | 91 N_LBRAC = 192, /* Start of lexical block */ 93 N_RBRAC = 224 /* End of lexical block */
|
/external/webkit/Source/WebCore/bindings/js/ |
JSDOMBinding.h | 125 // from which the object is being created, instead of assuming the lexical one. 126 // e.g. subframe.document.body should use the subframe's global object, not the lexical one.
|
/external/apache-xml/ |
NOTICE | 50 - Lexical Analyzer Generator (JLex) - see LICENSE.txt
|
/external/clang/include/clang/Lex/ |
TokenLexer.h | 79 /// Lexical information about the expansion point of the macro: the identifier
|
/external/clang/lib/StaticAnalyzer/Checkers/ |
ObjCUnusedIVarsChecker.cpp | 147 // FIXME: In the future hopefully we can just use the lexical DeclContext
|
/external/clang/utils/ |
FindSpecRefs | 39 ('6.4 Lexical elements', '49'), 232 ('A.1 Lexical grammar', '403'), 311 ('2 Lexical conventions', '15'), 562 ('A.2 Lexical conventions', '1085'), [all...] |