NodeBuilder Errors Guide 5-23
NCC# Description
173 Expression has no effect - discarded [NCC#173]
The compiler outputs this warning diagnostic when the optimizer
discards an expression. Examples of such expressions are:
x = y-1, z; /* y-1 is discarded */
a+3; /* a+3 is discarded */
x == 1? y: z; /* z is discarded */
174 Return value of function was ignored [NCC#174]
A function that has a return type (other than void) is used in an
expression, but the caller discards the return value without it being
used or stored. The warning can be removed by casting the return of
the function to void.
E
XAMPLE:
int f(void) {return 0;}
when (reset) {
(void)f();
}
175 This event will never be reached [NCC#175]
This message warns of the use of a specific, qualified event following
a generic, unqualified event in the same class. As the generic one
will catch the event first, the specific one will never evaluate to
TRUE. This condition can only occur when using the
scheduler_reset feature. (Failure to use the scheduler_reset
feature with multiple event expressions that are not exclusive can
result in unstable behavior.)
176 This event duplicates or overlaps a previous one [NCC#176]
In many cases, use of a when clause containing an event that is a
duplicate or an overlap of a previous event expression would prevent
the associated task from being executed, or may cause anomalous
behavior, with one task being executed sometimes, and the other
being executed the rest of the time.
(This latter behavior would occur as the result of round-robin
execution by the Neuron Chip firmware scheduler, if the
scheduler_reset feature were not used.)
177 Recommend use of ‘scheduler_reset’ feature [NCC#177]
The compiler makes this recommendation when there is a possibility
of anomalous execution of different tasks because the tasks'
respective when clauses are not mutually exclusive.
178
Cannot have any non-polled output network variables when
more than 14 bindable message tags are defined [NCC#178]
A Neuron Chip has up to 15 outgoing message ports. (Ports are also
known as “address table entries.”) Each bindable message tag
consumes one port, whether bound or not. Network variables can
share ports, but there must be at least one port available. This
message indicates that message tags are consuming all of the
address table entries, so no entries remain for network variables.
