Compiler error message

When the compiler encounters a syntax error it aborts the process for that script and displays a compiler error message in the Log window.

There are a couple of guidelines to remember when trying compiler error message

• The compiler reports the error when it can no longer make sense of the script: this often occurs on the line after the line containing the error.
• Several error messages end with "while compiling <include>.nss" even though the error is normally in the script being compiled not the included script.

B

Break outside of loop or case statement (while compiling <include>.nss)

[explanation]

E

Equality test has invalid operands (while compiling <include>.nss)

[explanation]

The include file is not normally the source of the error.

M

Mismatched types (while compiling <include>.nss)

1. The return type not matching function
2. A void function has been assigned to a variable, for example void function assigned to variable, string function assigned to int variable

The include file is not normally the source of the error.

N

No colon after case label 

[explanation]

No left bracket on arg list

[explanation]

Not all control paths return a value (while compiling <include>.nss)

1. A function does not have a return statement.
2. One or more of logic branches in a function does not have a return statement.
3. A function does not have an else or default case with a return function.

The include file is not normally the source of the error.

P

Parsing variable list

The statement terminator (;) is missing from the on previous line

U

Undefined identifier (<identifier>)

1. A variable is being used before it is defined
2. A string is missing its opening double-quotes mark

Unterminated string constant

1. A string is missing its closing double-quotes mark
2. A line contains a rouge double-quotes mark

V

Variable defined without type (while compiling <include>.nss)

[explanation]

The include file is not normally the source of the error.