Search

Home

Sort by

Searched defs:Identifiers (Results 1 - 6 of 6) sorted by relevance

/external/pdfium/xfa/fxfa/fm2js/
H A D	xfa_lexer.cpp	`393 iRet = Identifiers(p, m_ptr, pTemp); 459 uint32_t CXFA_FMLexer::Identifiers(CXFA_FMToken* t, function in class:CXFA_FMLexer`
/external/clang/lib/Parse/
H A D	ParseOpenMP.cpp	`47 SmallVector<Expr , 4> Identifiers; member in class:__anon1426::final 56 Identifiers.push_back(Res.get()); 58 llvm::ArrayRef<Expr > getIdentifiers() const { return Identifiers; }`
H A D	ParsePragma.cpp	`1215 SmallVector<Token, 5> Identifiers; local 1224 Identifiers.push_back(Tok); 1259 assert(!Identifiers.empty() && "Valid '#pragma unused' must have arguments"); 1267 PP.getPreprocessorAllocator().Allocate<Token>(2 * Identifiers.size()), 1268 2 * Identifiers.size()); 1269 for (unsigned i=0; i != Identifiers.size(); i++) { 1274 idTok = Identifiers[i];`
/external/libmojo/third_party/jinja2/
H A D	compiler.py	`101 class Identifiers(object): class in inherits:object 143 self.identifiers = Identifiers()`
/external/clang/include/clang/Lex/
H A D	Preprocessor.h	73 "Identifiers should be created by TokenValue(IdentifierInfo )"); 121 /// Identifiers for builtin macros and other builtins. 189 mutable IdentifierTable Identifiers; member in class:clang::Preprocessor 198 /// FIXME: Make sure the lifetime of Identifiers/Selectors isn't* tied to 697 IdentifierTable &getIdentifierTable() { return Identifiers; } 698 const IdentifierTable &getIdentifierTable() const { return Identifiers; } 794 return isMacroDefined(&Identifiers.get(Id)); 935 return &Identifiers.get(Name); 1553 /// Identifiers used for SEH handling in Borland. These are only
/external/python/cpython2/Lib/pydoc_data/
H A D	topics.py	5 'atom-identifiers': u'\nIdentifiers (Names)\n*****************\n\nAn identifier occurring as an atom is a name. See section Identifiers\nand keywords for lexical definition and section Naming and binding for\ndocumentation of naming and binding.\n\nWhen the name is bound to an object, evaluation of the atom yields\nthat object. When a name is not bound, an attempt to evaluate it\nraises a "NameError" exception.\n\nPrivate name mangling:** When an identifier that textually occurs in\na class definition begins with two or more underscore characters and\ndoes not end in two or more underscores, it is considered a private\nname of that class. Private names are transformed to a longer form\nbefore code is generated for them. The transformation inserts the\nclass name, with leading underscores removed and a single underscore\ninserted, in front of the name. For example, the identifier "__spam"\noccurring in a class named "Ham" will be transformed to "_Ham__spam".\nThis transformation is independent of the syntactical context in which\nthe identifier is used. If the transformed name is extremely long\n(longer than 255 characters), implementation defined truncation may\nhappen. If the class name consists only of underscores, no\ntransformation is done.\n', 42 'id-classes': u'\nReserved classes of identifiers\n******************************\n\nCertain classes of identifiers (besides keywords) have special\nmeanings. These classes are identified by the patterns of leading and\ntrailing underscore characters:\n\n"_"\n Not imported by "from module import ". The special identifier "_"\n is used in the interactive interpreter to store the result of the\n last evaluation; it is stored in the "__builtin__" module. When\n not in interactive mode, "_" has no special meaning and is not\n defined. See section The import statement.\n\n Note: The name "_" is often used in conjunction with\n internationalization; refer to the documentation for the\n "gettext" module for more information on this convention.\n\n"____"\n System-defined names. These names are defined by the interpreter\n and its implementation (including the standard library). Current\n system names are discussed in the Special method names section and\n elsewhere. More will likely be defined in future versions of\n Python. Any use of "____" names, in any context, that does not\n follow explicitly documented use, is subject to breakage without\n warning.\n\n"__"\n Class-private names. Names in this category, when used within the\n context of a class definition, are re-written to use a mangled form\n to help avoid name clashes between "private" attributes of base and\n derived classes. See section Identifiers (Names).\n', 43 'identifiers': u'\nIdentifiers and keywords\n***********************\n\nIdentifiers (also referred to as names) are described by the\nfollowing lexical definitions:\n\n identifier ::= (letter\|"_") (letter \| digit \| "_")\n letter ::= lowercase \| uppercase\n lowercase ::= "a"..."z"\n uppercase ::= "A"..."Z"\n digit ::= "0"..."9"\n\nIdentifiers are unlimited in length. Case is significant.\n\n\nKeywords\n========\n\nThe following identifiers are used as reserved words, or keywords of\nthe language, and cannot be used as ordinary identifiers. They must\nbe spelled exactly as written here:\n\n and del from not while\n as elif global or with\n assert else if pass yield\n break except import print\n class exec in raise\n continue finally is return\n def for lambda try\n\nChanged in version 2.4: "None" became a constant and is now recognized\nby the compiler as a name for the built-in object "None". Although it\nis not a keyword, you cannot assign a different object to it.\n\nChanged in version 2.5: Using "as" and "with" as identifiers triggers\na warning. To use them as keywords, enable the "with_statement"\nfuture feature .\n\nChanged in version 2.6: "as" and "with" are full keywords.\n\n\nReserved classes of identifiers\n===============================\n\nCertain classes of identifiers (besides keywords) have special\nmeanings. These classes are identified by the patterns of leading and\ntrailing underscore characters:\n\n"_"\n Not imported by "from module import ". The special identifier "_"\n is used in the interactive interpreter to store the result of the\n last evaluation; it is stored in the "__builtin__" module. When\n not in interactive mode, "_" has no special meaning and is not\n defined. See section The import statement.\n\n Note: The name "_" is often used in conjunction with\n internationalization; refer to the documentation for the\n "gettext" module for more information on this convention.\n\n"____"\n System-defined names. These names are defined by the interpreter\n and its implementation (including the standard library). Current\n system names are discussed in the Special method names section and\n elsewhere. More will likely be defined in future versions of\n Python. Any* use of "____" names, in any context, that does not\n follow explicitly documented use, is subject to breakage without\n warning.\n\n"__"\n Class-private names. Names in this category, when used within the\n context of a class definition, are re-written to use a mangled form\n to help avoid name clashes between "private" attributes of base and\n derived classes. See section Identifiers (Names).\n', namespace

Completed in 279 milliseconds