PYTHON List of Parser Tokens

is this article helpful?
|
Python replacement for PHP's List of Parser Tokens [ edit | history ]
source: http://docs.python.org/3/reference/lexical_analysis.html

2. Lexical analysis¶
A Python program is read by a parser.Input to the parser is a stream oftokens, generated by the lexical analyzer.This chapter describes how thelexical analyzer breaks a file into tokens.

Python reads program text as Unicode code points; the encoding of a source filecan be given by an encoding declaration and defaults to UTF-8, see PEP 3120for details.If the source file cannot be decoded, a SyntaxError israised.
2.1. Line structure¶
A Python program is divided into a number of logical lines.
2.1.1. Logical lines¶
The end of a logical line is represented by the token NEWLINE.Statementscannot cross logical line boundaries except where NEWLINE is allowed by thesyntax (e.g., between statements in compound statements). A logical line isconstructed from one or more physical lines by following the explicit orimplicit line joining rules.

2.1.2. Physical lines¶


A physical line is a sequence of characters terminated by an end-of-linesequence.In source files, any of the standard platform line terminationsequences can be used - the Unix form using ASCII LF (linefeed), the Windowsform using the ASCII sequence CR LF (return followed by linefeed), or the oldMacintosh form using the ASCII CR (return) character.All of these forms can beused equally, regardless of platform.

When embedding Python, source code strings should be passed to Python APIs usingthe standard C conventions for newline characters (the \n character,representing ASCII LF, is the line terminator).

2.1.3. Comments¶
A comment starts with a hash character (#) that is not part of a stringliteral, and ends at the end of the physical line.A comment signifies the endof the logical line unless the implicit line joining rules are invoked. Commentsare ignored by the syntax; they are not tokens.

2.1.4. Encoding declarations¶
If a comment in the first or second line of the Python script matches theregular expression coding\s*(+), this comment is processed as anencoding declaration; the first group of this expression names the encoding ofthe source code file. The recommended forms of this expression are
# -*- coding: <encoding-name> -*-




which is recognized also by GNU Emacs, and
# vim:fileencoding=<encoding-name>




which is recognized by Bram Moolenaar’s VIM.

If no encoding declaration is found, the default encoding is UTF-8.Inaddition, if the first bytes of the file are the UTF-8 byte-order mark(b'\xef\xbb\xbf'), the declared file encoding is UTF-8 (this is supported,among others, by Microsoft’s notepad).

If an encoding is declared, the encoding name must be recognized by Python. Theencoding is used for all lexical analysis, including string literals, commentsand identifiers. The encoding declaration must appear on a line of its own.

2.1.5. Explicit line joining¶
Two or more physical lines may be joined into logical lines using backslashcharacters (\), as follows: when a physical line ends in a backslash that isnot part of a string literal or comment, it is joined with the following forminga single logical line, deleting the backslash and the following end-of-linecharacter.For example:
if 1900 < year < 2100 and 1 <= month <= 12 \and 1 <= day <= 31 and 0 <= hour < 24 \and 0 <= minute < 60 and 0 <= second < 60:# Looks like a valid datereturn 1




A line ending in a backslash cannot carry a comment.A backslash does notcontinue a comment.A backslash does not continue a token except for stringliterals (i.e., tokens other than string literals cannot be split acrossphysical lines using a backslash).A backslash is illegal elsewhere on a lineoutside a string literal.

2.1.6. Implicit line joining¶


Expressions in parentheses, square brackets or curly braces can be split overmore than one physical line without using backslashes. For example:
month_names = ['Januari', 'Februari', 'Maart',# These are the'April','Mei','Juni',# Dutch names'Juli','Augustus', 'September',# for the months'Oktober', 'November', 'December']# of the year




Implicitly continued lines can carry comments.The indentation of thecontinuation lines is not important.Blank continuation lines are allowed.There is no NEWLINE token between implicit continuation lines.Implicitlycontinued lines can also occur within triple-quoted strings (see below); in thatcase they cannot carry comments.

2.1.7. Blank lines¶
A logical line that contains only spaces, tabs, formfeeds and possibly acomment, is ignored (i.e., no NEWLINE token is generated).During interactiveinput of statements, handling of a blank line may differ depending on theimplementation of the read-eval-print loop.In the standard interactiveinterpreter, an entirely blank logical line (i.e. one containing not evenwhitespace or a comment) terminates a multi-line statement.

2.1.8. Indentation¶
Leading whitespace (spaces and tabs) at the beginning of a logical line is usedto compute the indentation level of the line, which in turn is used to determinethe grouping of statements.

Tabs are replaced (from left to right) by one to eight spaces such that thetotal number of characters up to and including the replacement is a multiple ofeight (this is intended to be the same rule as used by Unix).The total numberof spaces preceding the first non-blank character then determines the line’sindentation.Indentation cannot be split over multiple physical lines usingbackslashes; the whitespace up to the first backslash determines theindentation.

Indentation is rejected as inconsistent if a source file mixes tabs and spacesin a way that makes the meaning dependent on the worth of a tab in spaces; aTabError is raised in that case.

Cross-platform compatibility note: because of the nature of text editors onnon-UNIX platforms, it is unwise to use a mixture of spaces and tabs for theindentation in a single source file.It should also be noted that differentplatforms may explicitly limit the maximum indentation level.

A formfeed character may be present at the start of the line; it will be ignoredfor the indentation calculations above.Formfeed characters occurring elsewherein the leading whitespace have an undefined effect (for instance, they may resetthe space count to zero).The indentation levels of consecutive lines are used to generate INDENT andDEDENT tokens, using a stack, as follows.

Before the first line of the file is read, a single zero is pushed on the stack;this will never be popped off again.The numbers pushed on the stack willalways be strictly increasing from bottom to top.At the beginning of eachlogical line, the line’s indentation level is compared to the top of the stack.If it is equal, nothing happens. If it is larger, it is pushed on the stack, andone INDENT token is generated.If it is smaller, it must be one of thenumbers occurring on the stack; all numbers on the stack that are larger arepopped off, and for each number popped off a DEDENT token is generated.At theend of the file, a DEDENT token is generated for each number remaining on thestack that is larger than zero.

Here is an example of a correctly (though confusingly) indented piece of Pythoncode:
def perm(l):# Compute the list of all permutations of lif len(l) <= 1:return [l]r = []for i in range(len(l)):s = l[:i] + l[i+1:]p = perm(s)for x in p:r.append(l[i:i+1] + x)return r




The following example shows various indentation errors:
 def perm(l):# error: first line indentedfor i in range(len(l)):# error: not indenteds = l[:i] + l[i+1:]p = perm(l[:i] + l[i+1:])# error: unexpected indentfor x in p:r.append(l[i:i+1] + x)return r# error: inconsistent dedent




(Actually, the first three errors are detected by the parser; only the lasterror is found by the lexical analyzer — the indentation of return r doesnot match a level popped off the stack.)

2.1.9. Whitespace between tokens¶


Except at the beginning of a logical line or in string literals, the whitespacecharacters space, tab and formfeed can be used interchangeably to separatetokens.Whitespace is needed between two tokens only if their concatenationcould otherwise be interpreted as a different token (e.g., ab is one token, buta b is two tokens).


2.2. Other tokens¶


Besides NEWLINE, INDENT and DEDENT, the following categories of tokens exist:identifiers, keywords, literals, operators, and delimiters. Whitespacecharacters (other than line terminators, discussed earlier) are not tokens, butserve to delimit tokens. Where ambiguity exists, a token comprises the longestpossible string that forms a legal token, when read from left to right.

2.3. Identifiers and keywords¶
Identifiers (also referred to as names) are described by the following lexicaldefinitions.

The syntax of identifiers in Python is based on the Unicode standard annexUAX-31, with elaboration and changes as defined below; see also PEP 3131 forfurther details.

Within the ASCII range (U+0001..U+007F), the valid characters for identifiersare the same as in Python 2.x: the uppercase and lowercase letters A throughZ, the underscore _ and, except for the first character, the digits0 through 9.

Python 3.0 introduces additional characters from outside the ASCII range (seePEP 3131).For these characters, the classification uses the version of theUnicode Character Database as included in the unicodedata module.

Identifiers are unlimited in length.Case is significant.
identifier ::=[url=#grammar-token-xid_start]xid_start[/url] [url=#grammar-token-xid_continue]xid_continue[/url]*id_start ::=<all characters in general categories Lu, Ll, Lt, Lm, Lo, Nl, the underscore, and characters with the Other_ID_Start property>id_continue  ::=<all characters in [url=#grammar-token-id_start]id_start[/url], plus characters in the categories Mn, Mc, Nd, Pc and others with the Other_ID_Continue property>xid_start ::=<all characters in [url=#grammar-token-id_start]id_start[/url] whose NFKC normalization is in "id_start xid_continue*">xid_continue ::=<all characters in [url=#grammar-token-id_continue]id_continue[/url] whose NFKC normalization is in "id_continue*">


The Unicode category codes mentioned above stand for:
  • Lu - uppercase letters
  • Ll - lowercase letters
  • Lt - titlecase letters
  • Lm - modifier letters
  • Lo - other letters
  • Nl - letter numbers
  • Mn - nonspacing marks
  • Mc - spacing combining marks
  • Nd - decimal numbers
  • Pc - connector punctuations
  • Other_ID_Start - explicit list of characters in PropList.txt to support backwards compatibility
  • Other_ID_Continue - likewise


All identifiers are converted into the normal form NFKC while parsing; comparisonof identifiers is based on NFKC.

A non-normative HTML file listing all valid identifier characters for Unicode4.1 can be found athttp://www.dcl.hpi.uni-potsdam.de/home/loewis/table-3131.html.
2.3.1. Keywords¶
The following identifiers are used as reserved words, or keywords of thelanguage, and cannot be used as ordinary identifiers.They must be spelledexactly as written here:
FalseclassfinallyisreturnNonecontinueforlambdatryTruedeffromnonlocalwhileanddelglobalnotwithaselififoryieldassertelseimportpassbreakexceptinraise




2.3.2. Reserved classes of identifiers¶


Certain classes of identifiers (besides keywords) have special meanings.Theseclasses are identified by the patterns of leading and trailing underscorecharacters:_*Not imported by from module import *.The special identifier _ is usedin the interactive interpreter to store the result of the last evaluation; it isstored in the builtins module.When not in interactive mode, _has no special meaning and is not defined. See section The import statement.NoteThe name _ is often used in conjunction with internationalization;refer to the documentation for the gettext module for moreinformation on this convention.
__*__System-defined names. These names are defined by the interpreter and itsimplementation (including the standard library).Current system names arediscussed in the Special method names section and elsewhere.More will likelybe defined in future versions of Python.Any use of __*__ names, inany context, that does not follow explicitly documented use, is subject tobreakage without warning.__*Class-private names.Names in this category, when used within the context of aclass definition, are re-written to use a mangled form to help avoid nameclashes between “private” attributes of base and derived classes. See sectionIdentifiers (Names).


2.4. Literals¶
Literals are notations for constant values of some built-in types.
2.4.1. String and Bytes literals¶
String literals are described by the following lexical definitions:
stringliteral ::=[[url=#grammar-token-stringprefix]stringprefix[/url]]([url=#grammar-token-shortstring]shortstring[/url] | [url=#grammar-token-longstring]longstring[/url])stringprefix ::="r" | "u" | "R" | "U"shortstring ::="'" [url=#grammar-token-shortstringitem]shortstringitem[/url]* "'" | '"' [url=#grammar-token-shortstringitem]shortstringitem[/url]* '"'longstring ::="'''" [url=#grammar-token-longstringitem]longstringitem[/url]* "'''" | '"""' [url=#grammar-token-longstringitem]longstringitem[/url]* '"""'shortstringitem ::=[url=#grammar-token-shortstringchar]shortstringchar[/url] | [url=#grammar-token-stringescapeseq]stringescapeseq[/url]longstringitem  ::=[url=#grammar-token-longstringchar]longstringchar[/url] | [url=#grammar-token-stringescapeseq]stringescapeseq[/url]shortstringchar ::=<any source character except "\" or newline or the quote>longstringchar  ::=<any source character except "\">stringescapeseq ::="\" <any source character>
bytesliteral ::=[url=#grammar-token-bytesprefix]bytesprefix[/url]([url=#grammar-token-shortbytes]shortbytes[/url] | [url=#grammar-token-longbytes]longbytes[/url])bytesprefix ::="b" | "B" | "br" | "Br" | "bR" | "BR" | "rb" | "rB" | "Rb" | "RB"shortbytes ::="'" [url=#grammar-token-shortbytesitem]shortbytesitem[/url]* "'" | '"' [url=#grammar-token-shortbytesitem]shortbytesitem[/url]* '"'longbytes ::="'''" [url=#grammar-token-longbytesitem]longbytesitem[/url]* "'''" | '"""' [url=#grammar-token-longbytesitem]longbytesitem[/url]* '"""'shortbytesitem ::=[url=#grammar-token-shortbyteschar]shortbyteschar[/url] | [url=#grammar-token-bytesescapeseq]bytesescapeseq[/url]longbytesitem  ::=[url=#grammar-token-longbyteschar]longbyteschar[/url] | [url=#grammar-token-bytesescapeseq]bytesescapeseq[/url]shortbyteschar ::=<any ASCII character except "\" or newline or the quote>longbyteschar  ::=<any ASCII character except "\">bytesescapeseq ::="\" <any ASCII character>


One syntactic restriction not indicated by these productions is that whitespaceis not allowed between the stringprefix or bytesprefix and therest of the literal. The source character set is defined by the encodingdeclaration; it is UTF-8 if no encoding declaration is given in the source file;see section Encoding declarations.In plain English: Both types of literals can be enclosed in matching single quotes(') or double quotes (").They can also be enclosed in matching groupsof three single or double quotes (these are generally referred to astriple-quoted strings).The backslash (\) character is used to escapecharacters that otherwise have a special meaning, such as newline, backslashitself, or the quote character.

Bytes literals are always prefixed with 'b' or 'B'; they produce aninstance of the bytes type instead of the str type.Theymay only contain ASCII characters; bytes with a numeric value of 128 or greatermust be expressed with escapes.

As of Python 3.3 it is possible again to prefix unicode strings with au prefix to simplify maintenance of dual 2.x and 3.x codebases.

Both string and bytes literals may optionally be prefixed with a letter 'r'or 'R'; such strings are called raw strings and treat backslashes asliteral characters.As a result, in string literals, '\U' and '\u'escapes in raw strings are not treated specially. Given that Python 2.x’s rawunicode literals behave differently than Python 3.x’s the 'ur' syntaxis not supported.
New in version 3.3: The 'rb' prefix of raw bytes literals has been added as a synonymof 'br'.New in version 3.3: Support for the unicode legacy literal (u'value') was reintroducedto simplify the maintenance of dual Python 2.x and 3.x codebases.See PEP 414 for more information.


In triple-quoted strings, unescaped newlines and quotes are allowed (and areretained), except that three unescaped quotes in a row terminate the string.(A“quote” is the character used to open the string, i.e. either ' or ".)Unless an 'r' or 'R' prefix is present, escape sequences in strings areinterpreted according to rules similar to those used by Standard C.Therecognized escape sequences are:
Escape SequenceMeaningNotes
\newline Backslash and newline ignored  
\\ Backslash (\)  
\' Single quote (')  
\" Double quote (")  
\a ASCII Bell (BEL)  
\b ASCII Backspace (BS)  
\f ASCII Formfeed (FF)  
\n ASCII Linefeed (LF)  
\r ASCII Carriage Return (CR)  
\t ASCII Horizontal Tab (TAB)  
\v ASCII Vertical Tab (VT)  
\ooo Character with octal valueooo (1,3)
\xhh Character with hex value hh (2,3)

Escape sequences only recognized in string literals are:
Escape SequenceMeaningNotes
\N{name} Character named name in theUnicode database (4)
\uxxxx Character with 16-bit hex valuexxxx (5)
\Uxxxxxxxx Character with 32-bit hex valuexxxxxxxx (6)

Notes:As in Standard C, up to three octal digits are accepted.Unlike in Standard C, exactly two hex digits are required.In a bytes literal, hexadecimal and octal escapes denote the byte with thegiven value. In a string literal, these escapes denote a Unicode characterwith the given value.Changed in version 3.3: Support for name aliases has been added.Individual code units which form parts of a surrogate pair can be encoded usingthis escape sequence.Exactly four hex digits are required.Any Unicode character can be encoded this way.Exactly eight hex digitsare required.Unlike Standard C, all unrecognized escape sequences are left in the stringunchanged, i.e., the backslash is left in the string.(This behavior isuseful when debugging: if an escape sequence is mistyped, the resulting outputis more easily recognized as broken.)It is also important to note that theescape sequences only recognized in string literals fall into the category ofunrecognized escapes for bytes literals.

Even in a raw string, string quotes can be escaped with a backslash, but thebackslash remains in the string; for example, r"\"" is a valid stringliteral consisting of two characters: a backslash and a double quote; r"\"is not a valid string literal (even a raw string cannot end in an odd number ofbackslashes).Specifically, a raw string cannot end in a single backslash(since the backslash would escape the following quote character).Note alsothat a single backslash followed by a newline is interpreted as those twocharacters as part of the string, not as a line continuation.

2.4.2. String literal concatenation¶


Multiple adjacent string or bytes literals (delimited by whitespace), possiblyusing different quoting conventions, are allowed, and their meaning is the sameas their concatenation.Thus, "hello" 'world' is equivalent to"helloworld".This feature can be used to reduce the number of backslashesneeded, to split long strings conveniently across long lines, or even to addcomments to parts of strings, for example:
re.compile("[A-Za-z_]"# letter or underscore"[A-Za-z0-9_]*"# letter, digit or underscore)




Note that this feature is defined at the syntactical level, but implemented atcompile time.The ‘+’ operator must be used to concatenate string expressionsat run time.Also note that literal concatenation can use different quotingstyles for each component (even mixing raw strings and triple quoted strings).

2.4.3. Numeric literals¶
There are three types of numeric literals: integers, floating point numbers, andimaginary numbers.There are no complex literals (complex numbers can be formedby adding a real number and an imaginary number).

Note that numeric literals do not include a sign; a phrase like -1 isactually an expression composed of the unary operator ‘-‘ and the literal1.

2.4.4. Integer literals¶


Integer literals are described by the following lexical definitions:
integer ::=[url=#grammar-token-decimalinteger]decimalinteger[/url] | [url=#grammar-token-octinteger]octinteger[/url] | [url=#grammar-token-hexinteger]hexinteger[/url] | [url=#grammar-token-bininteger]bininteger[/url]decimalinteger ::=[url=#grammar-token-nonzerodigit]nonzerodigit[/url] [url=#grammar-token-digit]digit[/url]* | "0"+nonzerodigit ::="1"..."9"digit ::="0"..."9"octinteger ::="0" ("o" | "O") [url=#grammar-token-octdigit]octdigit[/url]+hexinteger ::="0" ("x" | "X") [url=#grammar-token-hexdigit]hexdigit[/url]+bininteger ::="0" ("b" | "B") [url=#grammar-token-bindigit]bindigit[/url]+octdigit ::="0"..."7"hexdigit ::=[url=#grammar-token-digit]digit[/url] | "a"..."f" | "A"..."F"bindigit ::="0" | "1"


There is no limit for the length of integer literals apart from what can bestored in available memory.

Note that leading zeros in a non-zero decimal number are not allowed. This isfor disambiguation with C-style octal literals, which Python used before version3.0.

Some examples of integer literals:
721474836470o1770b1001101113792281625142643375935439503360o3770x100000000792281625142643375935439503360xdeadbeef




2.4.5. Floating point literals¶


Floating point literals are described by the following lexical definitions:
floatnumber ::=[url=#grammar-token-pointfloat]pointfloat[/url] | [url=#grammar-token-exponentfloat]exponentfloat[/url]pointfloat ::=[[url=#grammar-token-intpart]intpart[/url]] [url=#grammar-token-fraction]fraction[/url] | [url=#grammar-token-intpart]intpart[/url] "."exponentfloat ::=([url=#grammar-token-intpart]intpart[/url] | [url=#grammar-token-pointfloat]pointfloat[/url]) [url=#grammar-token-exponent]exponent[/url]intpart ::=[url=#grammar-token-digit]digit[/url]+fraction ::="." [url=#grammar-token-digit]digit[/url]+exponent ::=("e" | "E") ["+" | "-"] [url=#grammar-token-digit]digit[/url]+


Note that the integer and exponent parts are always interpreted using radix 10.For example, 077e010 is legal, and denotes the same number as 77e10. Theallowed range of floating point literals is implementation-dependent. Someexamples of floating point literals:
3.1410..0011e1003.14e-100e0




Note that numeric literals do not include a sign; a phrase like -1 isactually an expression composed of the unary operator - and the literal1.

2.4.6. Imaginary literals¶


Imaginary literals are described by the following lexical definitions:
imagnumber ::=([url=#grammar-token-floatnumber]floatnumber[/url] | [url=#grammar-token-intpart]intpart[/url]) ("j" | "J")


An imaginary literal yields a complex number with a real part of 0.0.Complexnumbers are represented as a pair of floating point numbers and have the samerestrictions on their range.To create a complex number with a nonzero realpart, add a floating point number to it, e.g., (3+4j).Some examples ofimaginary literals:
3.14j10.j10j.001j1e100j3.14e-10j





2.5. Operators¶
The following tokens are operators:
+-***//%<<>>&|^~<><=>===!=




2.6. Delimiters¶
The following tokens serve as delimiters in the grammar:
()[]{},:.;@=+=-=*=/=/=%=&=|=^=>>=<<=**=



The period can also occur in floating-point and imaginary literals.A sequenceof three periods has a special meaning as an ellipsis literal. The second halfof the list, the augmented assignment operators, serve lexically as delimiters,but also perform an operation.

The following printing ASCII characters have special meaning as part of othertokens or are otherwise significant to the lexical analyzer:
'"#\




The following printing ASCII characters are not used in Python.Theiroccurrence outside string literals and comments is an unconditional error:
$?`

Footnotes
http://www.unicode.org/Public/6.1.0/ucd/NameAliases.txt

PHP List of Parser Tokens

PHP original manual for List of Parser Tokens [ show | php.net ]

List of Parser Tokens

Various parts of the PHP language are represented internally by types like T_SR. PHP outputs identifiers like this one in parse errors, like "Parse error: unexpected T_SR, expecting ',' or ';' in script.php on line 10."

You're supposed to know what T_SR means. For everybody who doesn't know that, here is a table with those identifiers, PHP-syntax and references to the appropriate places in the manual.

Tokens
Token Syntax Reference
T_ABSTRACT abstract Class Abstraction (available since PHP 5.0.0)
T_AND_EQUAL &= assignment operators
T_ARRAY array() array(), array syntax
T_ARRAY_CAST (array) type-casting
T_AS as foreach
T_BAD_CHARACTER   anything below ASCII 32 except \t (0x09), \n (0x0a) and \r (0x0d)
T_BOOLEAN_AND && logical operators
T_BOOLEAN_OR || logical operators
T_BOOL_CAST (bool) or (boolean) type-casting
T_BREAK break break
T_CASE case switch
T_CATCH catch Exceptions (available since PHP 5.0.0)
T_CHARACTER    
T_CLASS class classes and objects
T_CLASS_C __CLASS__ magic constants (available since PHP 4.3.0)
T_CLONE clone classes and objects (available since PHP 5.0.0)
T_CLOSE_TAG ?> or %>  
T_COMMENT // or #, and /* */ in PHP 5 comments
T_CONCAT_EQUAL .= assignment operators
T_CONST const  
T_CONSTANT_ENCAPSED_STRING "foo" or 'bar' string syntax
T_CONTINUE continue  
T_CURLY_OPEN    
T_DEC -- incrementing/decrementing operators
T_DECLARE declare declare
T_DEFAULT default switch
T_DIR __DIR__ magic constants (available since PHP 5.3.0)
T_DIV_EQUAL /= assignment operators
T_DNUMBER 0.12, etc floating point numbers
T_DOC_COMMENT /** */ PHPDoc style comments (available since PHP 5.0.0)
T_DO do do..while
T_DOLLAR_OPEN_CURLY_BRACES ${ complex variable parsed syntax
T_DOUBLE_ARROW => array syntax
T_DOUBLE_CAST (real), (double) or (float) type-casting
T_DOUBLE_COLON :: see T_PAAMAYIM_NEKUDOTAYIM below
T_ECHO echo echo()
T_ELSE else else
T_ELSEIF elseif elseif
T_EMPTY empty empty()
T_ENCAPSED_AND_WHITESPACE    
T_ENDDECLARE enddeclare declare, alternative syntax
T_ENDFOR endfor for, alternative syntax
T_ENDFOREACH endforeach foreach, alternative syntax
T_ENDIF endif if, alternative syntax
T_ENDSWITCH endswitch switch, alternative syntax
T_ENDWHILE endwhile while, alternative syntax
T_END_HEREDOC   heredoc syntax
T_EVAL eval() eval()
T_EXIT exit or die exit(), die()
T_EXTENDS extends extends, classes and objects
T_FILE __FILE__ magic constants
T_FINAL final Final Keyword (available since PHP 5.0.0)
T_FOR for for
T_FOREACH foreach foreach
T_FUNCTION function or cfunction functions
T_FUNC_C __FUNCTION__ magic constants (available since PHP 4.3.0)
T_GLOBAL global variable scope
T_GOTO goto undocumented (available since PHP 5.3.0)
T_HALT_COMPILER __halt_compiler() __halt_compiler (available since PHP 5.1.0)
T_IF if if
T_IMPLEMENTS implements Object Interfaces (available since PHP 5.0.0)
T_INC ++ incrementing/decrementing operators
T_INCLUDE include() include()
T_INCLUDE_ONCE include_once() include_once()
T_INLINE_HTML    
T_INSTANCEOF instanceof type operators (available since PHP 5.0.0)
T_INT_CAST (int) or (integer) type-casting
T_INTERFACE interface Object Interfaces (available since PHP 5.0.0)
T_ISSET isset() isset()
T_IS_EQUAL == comparison operators
T_IS_GREATER_OR_EQUAL >= comparison operators
T_IS_IDENTICAL === comparison operators
T_IS_NOT_EQUAL != or <> comparison operators
T_IS_NOT_IDENTICAL !== comparison operators
T_IS_SMALLER_OR_EQUAL <= comparison operators
T_LINE __LINE__ magic constants
T_LIST list() list()
T_LNUMBER 123, 012, 0x1ac, etc integers
T_LOGICAL_AND and logical operators
T_LOGICAL_OR or logical operators
T_LOGICAL_XOR xor logical operators
T_METHOD_C __METHOD__ magic constants (available since PHP 5.0.0)
T_MINUS_EQUAL -= assignment operators
T_ML_COMMENT /* and */ comments (PHP 4 only)
T_MOD_EQUAL %= assignment operators
T_MUL_EQUAL *= assignment operators
T_NS_C __NAMESPACE__ namespaces. Also defined as T_NAMESPACE (available since PHP 5.3.0)
T_NEW new classes and objects
T_NUM_STRING    
T_OBJECT_CAST (object) type-casting
T_OBJECT_OPERATOR -> classes and objects
T_OLD_FUNCTION old_function  
T_OPEN_TAG <?php, <? or <% escaping from HTML
T_OPEN_TAG_WITH_ECHO <?= or <%= escaping from HTML
T_OR_EQUAL |= assignment operators
T_PAAMAYIM_NEKUDOTAYIM :: ::. Also defined as T_DOUBLE_COLON.
T_PLUS_EQUAL += assignment operators
T_PRINT print() print()
T_PRIVATE private classes and objects (available since PHP 5.0.0)
T_PUBLIC public classes and objects (available since PHP 5.0.0)
T_PROTECTED protected classes and objects (available since PHP 5.0.0)
T_REQUIRE require() require()
T_REQUIRE_ONCE require_once() require_once()
T_RETURN return returning values
T_SL << bitwise operators
T_SL_EQUAL <<= assignment operators
T_SR >> bitwise operators
T_SR_EQUAL >>= assignment operators
T_START_HEREDOC <<< heredoc syntax
T_STATIC static variable scope
T_STRING    
T_STRING_CAST (string) type-casting
T_STRING_VARNAME    
T_SWITCH switch switch
T_THROW throw Exceptions (available since PHP 5.0.0)
T_TRY try Exceptions (available since PHP 5.0.0)
T_UNSET unset() unset()
T_UNSET_CAST (unset) type-casting (available since PHP 5.0.0)
T_USE use namespaces (available since PHP 5.3.0)
T_VAR var classes and objects
T_VARIABLE $foo variables
T_WHILE while while, do..while
T_WHITESPACE    
T_XOR_EQUAL ^= assignment operators

See also token_name().