Echelon Neuron - Manual (Page 91)

Neuron Tools Errors Guide 83
NCC# Description
273 Procedure code generation label resources exhausted [NCC#273]
Code generation is performed on a procedure-by-procedure basis. The
compiler reuses certain internal resources during code generation of each
procedure. One of these resources is internal label markers. There are
only a limited number of labels that can be used in a given procedure.
These labels are used in each possible branching scenario, in loops, if
statements, ?: operators, and switch statements. By far the most common
cause of this message is a very large procedure containing a switch
statement with many cases. The simplest recourse is to split the switch
statement into two or more switch statements, and move each to a separate
subprocedure.
274 Use of possibly unitialized variable [NCC#274]
The Neuron C compiler tracks the use of automatic variables (those which
are local to a function or procedure, or a sub-scope of a function or
procedure). If such a variable is accessed (read) prior to its having been
stored (written), this warning is issued. Structure fields and array
elements are not individually tracked.
275 Recommend use of 'fails' or 'succeeds' event instead [NCC#275]
This message indicates that the call to a completion event can be changed
to a fails or succeeds event as an efficiency consideration. See the
discussion on events in the
Neuron C Programmer’s Guide or the Neuron C
Reference Guide .
276 The 'preempt_safe' keyword has no effect on this 'when' clause [NCC#276]
Some when clauses and their associated tasks will be executed regardless
of preemption mode. Use of the preempt_safe keyword for this type of
when clause is unnecessary, and has no effect.
291 Improper binary constant ‘<value>’ [NCC#291]
A binary constant begins with 0b and is followed by one or more binary
digits (0 or 1).
292 Incomplete hexadecimal constant ‘<value>’ [NCC#292]
A hexadecimal constant begins with 0x and must be followed by one or
more hexadecimal digits (0-9 and the letters a-f or A-F).
293 Improper octal constant ‘<value>’ [NCC#293]
An octal constant begins with 0, and must be followed by one or more octal
digits (0-7).