Echelon Neuron - Manual (Page 59)

Neuron Tools Errors Guide 51
NCC# Description
47 Type qualifier ‘volatile’ was ignored [NCC#47]
This keyword has no effect in Neuron C. To work with variables that are
asynchronously accessed from interrupt -tasks and when -tasks, use the
__lock construct for coordinated access.
48 Floating point is not supported [NCC#48]
Neuron C does not support floating point built-in data types and operators.
Use the floating point library functions instead. See the Functions chapter
in the Neuron C Reference Guide for more information on using the floating
point library, and the standard include file <float.h>.
49 Invalid array bounds [NCC#49]
In Neuron C, an array bound constant-expression must resolve to a positive
integer no larger than 32767.
50 Bitfield size must be from 0 to 8 bits [NCC#50]
A bitfield must fit inside an int type. Since in Neuron C an int is 8 bits, the
bitfield is also limited to 8 bits. Note that in ANSI C a bitfield size of 0 bits
is legal for an unnamed bitfield. Such a bitfield forces alignment to the
next storage unit boundary (which is a byte in Neuron C, since the Neuron
Chip architecture does not force any multi-byte data alignment.).
51 Bitfield type is incorrect [NCC#51]
A bitfield may only be declared using only a combination of the type
keywords int, signed, unsigned, long, short, and char. Bitfields may not be
arrays, pointers, structures, unions, or any other Neuron C type.
52 Bitfield size cannot be 0 unless unnamed [NCC#52]
In ANSI C a bitfield size of 0 bits is legal for an unnamed bitfield. Such a
bitfield forces alignment to the next storage unit boundary (which is a byte
in Neuron C, since the Neuron Chip architecture does not force any multi-
byte data alignment.).
53 Keyword ‘polled’ is ignored for input network variable [NCC#53]
The polled keyword only applies to output network variables. This
restriction does not apply to the case of model file compilation that is used
within the ShortStack, FTXL, or LIBILON development environment.
54 Repeated bind_info option [NCC#54]
The bind_info keyword is followed by a parenthesized list of one or more
options, some with associated values. Each keyword may appear at most
once.