(W) Variable Is Not Used; Compiler Errors; A "<Symbol>" Was Expected; Active Keyword Expected - AMX NETLINX PROGRAMMING LANGUAGE Manual

Compiler Messages

(w) Variable is not used

This warning occurs at the end of compilation for each variable that was declared but never used.

Compiler Errors

The compiler informs you when it finds an error during the compilation process. Most of the time these
errors occur due to a typographical error or incorrect syntax of a particular command. Unlike warnings,
errors must be corrected before your NetLinx program can be executed. The table below lists all of the
messages that can occur when there is an error during the compilation of your program.
A "<symbol>" was expected
The compiler is expecting a certain symbol at this particular place.

ACTIVE keyword expected

An ACTIVE keyword is not present after a SELECT keyword.

Allowed only in DEFINE_START

A keyword that is only allowed to appear in the DEFINE_START section of the program was
encountered elsewhere.

Attempted CALL to undefined subroutine

A CALL statement refers to a subroutine that has not been defined with a DEFINE_CALL statement.

Comment never ends, EOF encountered

A comment begins but never ends. Place a close comment, * ) at the end of the unfinished comment.

Conditional compile nesting too deep

There are too many nested #IF_DEFINED or #IF_NOT_DEFINED conditional compilation statements.
The limit is 20 nested conditional compilation statements.

Constant type not allowed

A constant value was declared as latching, toggling, or mutually exclusive, as shown below:
DEFINE_CONSTANT
PLAY = 1
DEFINE_LATCHING
PLAY (* Error: PLAY is a constant *)

DEFINE_CALL must have a name

DEFINE_CALL must have a name after it. For example, DEFINE_CALL 'VHS' .

DEFINE_CALL name already used

The name of the DEFINE_CALL has already been used. This name cannot be the same as an already
declared identifier of any type.

Device values must be equal

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 symbol

Duplicate definitions of variables or constants are found. All variables and constants must have unique
identifiers.
168 NetLinx Programming Language Reference Guide