NodeBuilder Errors Guide 5-11
NCC# Description
59 Expression type mismatch [NCC#59]
These error diagnostics result from combining expressions of
conflicting types, such as assigning an int to a pointer, or a pointer of
one type to a pointer to another type, or in using objects that have no
value (such as message tags or I/O object names) in expressions.
In many cases in ANSI C, you must use an explicit type cast.
However, note that casting should be avoided if possible, as it is often
masking poor programming practice.
60 Invalid subscript operation [NCC#60]
The compiler outputs this diagnostic when an array-index operator
[ expr ] is applied to a variable that is not a pointer or an array.
61 Object is not a struct/union pointer [NCC#61]
The compiler outputs this message when the left-hand side of the ->
operator is not a pointer to a struct or union type.
62 Object is not a structure or union [NCC#62]
The compiler outputs this message when the left-hand side of the dot
(.) operator is not a struct or union type.
63 Invalid cast operation [NCC#63]
Some conversions between data types are not permitted, even via an
explicit cast. For example, an object cannot be cast if its base type is
not known. Nor can an object be cast to void and then used in an
expression.
64 Cannot remove ‘const’ attribute via cast operation [NCC#64]
To prevent data that is declared constant from being modified,
Neuron C will not permit pointers including the const attribute from
being cast such that the const attribute is removed. Neither does
the compiler permit an implicit conversion of pointer (via function
call, etc.) such that the const attribute would be removed. However,
use of the #pragma relaxed_casting_on changes this error into a
warning. See the Compiler Directives chapter in the Neuron C
Reference Guide for more information on this pragma.
65 Cannot compute ‘sizeof’ for object [NCC#65]
The compiler attempted to calculate the size of a type, but did not
have enough information. This could result from a sizeof expression
for an object like a timer object, or a message tag, or a typedef name
which is a bind_info, or some similar circumstance.
66 Message object reference cannot be assigned to [NCC#66]
The message objects msg_in and resp_in are read-only. Attempts
to use these objects on the left side of an assignment statement result
in the diagnostic message above.
67 Pulsecount I/O object cannot use clock 0 [NCC#67]
The pulsecount I/O object does not support use of clock 0. Its use
will produce an indeterminate number of output pulses.
