AMX Axcess, Instruction Manual, Page: 118 / 144

Compiler Error Messages
110
Axcess Programming Language
Compiler Error Messages (Cont.)
Library file not found The library file containing the specified
SYSTEM_CALL could not be found.
Maximum string length exceeded String literals are limited in length to 132 charac-
ters, including spaces.
Must be char array reference An array type variable was expected in
CREATE_BUFFER, CREATE_MULTI_BUFFER, or
CLEAR_BUFFER.
Must be integer reference The identifier in question must be an integer. This
error occurs when the third parameter of
CREATE_LEVEL is an array or array element.
Out of memory The compiler has run out of memory. Free up mem-
ory either by removing any pop-up programs or
drivers, by using extended memory, or by breaking
your program into one or more include files.
Parameter mismatch in Call A value or variable passed to a CALL as a parame-
ter is of the wrong type as defined by the
DEFINE_CALL statement.
Program_Name must be on line 1 Move the PROGRAM_NAME= statement to the
first line of the program.
Push/Release not allowed within Push/Release A PUSH or RELEASE statement was found within
a block of code headed by a PUSH or RELEASE
statement.
Push/Release not allowed within Wait
Push_Channel not allowed within Wait
Release_Channel not allowed within Wait
Push_Device not allowed within Wait
Release_Device not allowed within Wait
These keywords are not allowed in a section of
code which will be executed due to a WAIT key-
word.
String constant expected A string is required for the particular operation. This
error occurs if a string literal enclosed in single
quotes does not follow the PROGRAM_NAME key-
word.
String constant never ends, EOF encountered A string literal is started but never ends. Add a clos-
ing single quotation mark (') to the end of the string.
String literal expected A string is required for the particular operation. This
error would occur if a string literal enclosed in sin-
gle quotes does not follow the #WARN keyword.
Subroutine may not call itself A subroutine cannot call itself. It can, however, call
a different subroutine.
Syntax error A syntax error is found in an expression. In most
cases, this error means that a character is out of
place or something is misspelled.
System_Call name not same as Program_Name in <file> This error occurs when a library file is compiled and
the name of the subroutine in the library file does
not match the PROGRAM_NAME string on the first
line of the file.
This variable type not allowed This error occurs when an attempt is made to use
an array variable with DEFINE_LATCHING,
DEFINE_TOGGLING, or
DEFINE_MUTUALLY_EXCLUSIVE.
To not allowed within Define_Start
To not allowed within mainline
To not allowed within Release
To not allowed within Wait
These errors occur if the TO keyword is found in an
erroneous location. The TO keyword can only be
associated directly with a PUSH statement.