5-58 Neuron C Compiler Errors (NCC)
NCC# Description
462 Global property cannot inherit conflicting types [NCC#462]
When a configuration property is declared using the global keyword,
it is shared among multiple network variables (or functional blocks).
Some CPTs are incomplete type definitions, and the configuration
properties that use these CPTs in their declarations inherit their
types from the network variables they apply to. If a global
configuration property is used as a property of two or more network
variables of different types, there is a resulting conflict in the type
inheritance. This situation is not permitted.
463
464
The ‘const’ attribute has been removed by cast operations
[NCC#463]
Pointer to constant data has been cast into pointer to non-
const data [NCC#464]
These warning messages inform the programmer of a potential
programming error, because an attempt to write to read-only
memory may occur. Writes to read-only memory do not cause
problems, other than that the expected write does not occur.
465
466
SD string not acceptable in ShortStack for LonMark
[NCC#465]
Node’s SD string not acceptable in ShortStack for LonMark
[NCC#466]
The SD string specified is not acceptable in a program that is used as
a Neuron C model file for ShortStack host development. Consult the
ShortStack User's Guide for more information.
467
468
Invalid fblock member number specification [NCC#467]
The implementation-specific member’s number conflicts with
another member [NCC#468]
A Neuron C program's implementation of an FPT (a profile) can add
one or more members not present in the FPT. These members are
called implementation-specific. Such members must specify a
member name and a member number since there is no FPT record to
provide this information for the compiler. The member name and
member number supplied in the implementation_specific
statement must be unique, and must not conflict with any FPT
members, nor any other implementation-specific members. Since a
user FPT can inherit from a standard FPT, the implementation-
specific members must be unique within both the user FPT and the
standard FPT in this situation.
469
The number of FPT members exceeds the compiler’s capacity
[NCC#469]
The compiler accepts a maximum of 4096 members per FPT.
