Compiler Error Messages - AMX AXCESS CONTROL SYSTEM PROGRAM Instruction Manual

Compiler Error Messages

This section lists all of the messages that can occur when there is an error during the compilation of
your program. Unlike warnings, errors must be corrected before your Axcess program can be
executed.
Compiler Error Messages
Error
A "<symbol>" was expected
Active keyword expected
Allowed only in Define_Start
Attempted Call to undefined subroutine
Comment never ends, EOF encountered
Conditional compile nesting too deep
Constant type not allowed
Define_Call must have a name
Define_Call name already used
Device values must be equal
Duplicate symbol
Evaluation stack overflow
Evaluation stack underflow
Identifier expected
Identifier is not an array type
Include file not found
Invalid include file name
Axcess Programming Language
Compiler Error Messages
Description
The compiler is expecting a certain symbol at this
particular place.
An ACTIVE keyword is not present after a SELECT
keyword.
A keyword that is only allowed to appear in the
DEFINE_START section of the program was
encountered elsewhere.
A CALL statement refers to a subroutine that has
not been defined with a DEFINE_CALL statement.
A comment begins but never ends. Place a close
comment, *) at the end of the unfinished comment.
There are too many nested #IF_DEFINED or
#IF_NOT_DEFINED conditional compilation state-
ments. The limit is 20 nested conditional compila-
tion statements.
A constant value was declared as latching, tog-
gling, or mutually exclusive, as shown below:
DEFINE_CONSTANT
PLAY = 1
DEFINE_LATCHING
PLAY (*Error: PLAY is a constant
*)
DEFINE_CALL must have a name after it. For
example, DEFINE_CALL 'VHS'.
The name of the DEFINE_CALL has already been
used. This name cannot be the same as an already
declared identifier of any type.
In a range specification, the devices (or their
defined identifiers) must be equal. For example,
([1,1]..[1,5]) is valid; ([1,1]..[2,5]) is not.
Duplicate definitions of variables or constants are
found. All variables and constants must have
unique identifiers.
The expression is too complicated. Try breaking it
up into smaller pieces.
The compiler is expecting an identifier after a
#DEFINE statement or after an integer declaration
in the DEFINE_VARIABLE section.
A non-array variable was treated as an array.
An INCLUDE statement was encountered, but the
specified include file could not be found.
A string literal enclosed in single quotes must follow
the INCLUDE keyword.
109