Compiler Messages
170
NetLinx Programming Language Reference Guide
PUSH_CHANNEL not allowed within Wait
These keywords are not allowed in a section of code which will be executed due to a WAIT keyword.
RELEASE_CHANNEL not allowed within Wait
These keywords are not allowed in a section of code which will be executed due to a WAIT keyword.
PUSH_DEVICE not allowed within Wait
These keywords are not allowed in a section of code which will be executed due to a WAIT keyword.
RELEASE_DEVICE not allowed within Wait
These keywords are not allowed in a section of code which will be executed due to a WAIT keyword.
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 keyword.
String constant never ends, EOF encountered
A string literal is started but never ends. Add a closing 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
single 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 statements that occur outside the data flow of PUSH events/statements may not
work
TO is valid:
 Under a PUSH statement
 Under a BUTTON_EVENT/PUSH handler
 Under a BUTTON_EVENT/HOLD handler
 In a DEFINE_FUNCTION or DEFINE_CALL that gets invoked in one of the areas above. In
this case, the function or call could be potentially be invoked anywhere in the program. It is
an intractable problem to check for misplacement of <any possible function name> and <any
possible call name>, so TO outside of PUSH'es will not generate an error, just a warning.
To Next Page
Loading...
Need help?
General
