KW_ACCESS_EQ some keywords specified here are only keywords
when they are succeeded or preceeded by another keyword.
For the sake of simplicity, we assume all of these words
are keywords.
final public static BaseTokenID ERR_INCOMPLETE_STRING_LITERAL(Code)
ERR_INVALID_BINARY_LITERAL
final public static BaseTokenID ERR_INVALID_BINARY_LITERAL(Code)
ERR_INVALID_CHAR
final public static BaseTokenID ERR_INVALID_CHAR(Code)
ERR_INVALID_HEX_LITERAL
final public static BaseTokenID ERR_INVALID_HEX_LITERAL(Code)
ERR_INVALID_INTEGER
final public static BaseTokenID ERR_INVALID_INTEGER(Code)
ERR_INVALID_OCTAL_LITERAL
final public static BaseTokenID ERR_INVALID_OCTAL_LITERAL(Code)
EXCLAMATION
final public static BaseImageTokenID EXCLAMATION(Code)
SC_EXCLAMATION in here is just a place holder to show that it is
a special character the sysntax highlighting for exclamations are
handled in LINE_COMMENT
final public static BaseImageTokenID KW_ACCESS_EQ(Code)
some keywords specified here are only keywords
when they are succeeded or preceeded by another keyword.
For the sake of simplicity, we assume all of these words
are keywords. The table below lists these keywords:
assumed keyword complete keyword
block block data
double double precision
file end file
go go to
precision double precision
procedure module procedure
select select case, end select
to go to
final public static BaseTokenID NUM_LITERAL_BINARY(Code)
NUM_LITERAL_BINARY_ID
final public static int NUM_LITERAL_BINARY_ID(Code)
NUM_LITERAL_COMPLEX
final public static BaseTokenID NUM_LITERAL_COMPLEX(Code)
NUM_LITERAL_COMPLEX in here is just a place holder to show that it is a
valid numeric literal
the sysntax highlighting for complex numbers are handled
in integers,reals and paranthesis
NUM_LITERAL_COMPLEX_ID
final public static int NUM_LITERAL_COMPLEX_ID(Code)
NUM_LITERAL_HEX
final public static BaseTokenID NUM_LITERAL_HEX(Code)