Compiler Messages
171
NetLinx Programming Language Reference Guide
Too few parameters in CALL
There are not enough parameters being passed to the subroutine.
Too many include files
In NetLinx, the number of Include files allowed is limited only by the amount of memory available on
the PC at compile time.
Too many parameters in CALL
There are too many parameters being passed to the subroutine.
Type mismatch in function CALL
A function was called with a parameter of the wrong type. For instance, attempting to use ITOA with an
array as a parameter will result in an error.
Undefined identifier
An attempt was made to reference an identifier that has not been defined previously in the program.
Unmatched #END_IF
An #END_IF keyword was found, but no #IF_DEFINED or #IF_NOT_DEFINED was previously
compiled.
Unrecognized character in input file
An invalid character was found during the build.
Use SYSTEM_CALL [instance] 'name'
This error occurs if a SYSTEM_CALL statement is written incorrectly as SYSTEM_CALL 'NAME'
[INSTANCE NUMBER].
Variable assignment not allowed here
Variables may not be assigned a value when they are defined in the DEFINE_VARIABLE section.
Wait not found
A statement references a WAIT by a name that does not exist. For example, CANCEL_WAIT 'CASS'
will produce this error if there is no WAIT named CASS.
Run-Time Errors
In many cases, a program is compiled and sent to the Central Controller error-free, but the system does
not act in the way it should. If the program code is correct, you should check for run-time errors. These
errors occur in the Central Controller, usually when it could not perform a particular operation in the
program.
Bad assign 2dim...
These errors occur if an attempt is made to assign a two-dimensional array to a different type (such as a
variable or one-dimensional array), and vice versa.
This all applies to MIN_TO also.
To Next Page
Loading...
Need help?
General
