Echelon Neuron - Manual (Page 3)

Neuron Tools Errors Guide iii
Welcome
This document describes various warning and error messages that can occur
when using Echelon ® development tools, such as the NodeBuilder ® FX
Development Tool, Mini FX Evaluation Kit, ShortStack ® Developer’s Kit, FTXL ™
Developer’s Kit, and LonTalk ® Interface Developer (LID) utility.
Audience
This guide is intended for users of Echelon development tools.
Content
This guide describes the error messages that you can encounter while using
Echelon development tools. This guide organizes the errors into separate
chapters with each chapter containing errors applicable to a single software
component. For example, compiler errors are in one chapter and NodeBuilder
interface errors are in another chapter.
The error messages described in this document include hints, warnings, errors,
and fatal errors:
• Hints are informative messages that suggest improvements for your
implementation.
• Warnings are not severe enough to prevent successful compilation, but
they should each be examined, and corrected as appropriate. Any code
that is flagged by the compiler with a warning message should be viewed
as a potential programming error, or at least as a poor programming
practice.
• Errors result from code constructs that cannot be interpreted by the
compiler, or indicate situations that are expressly prohibited by either
the ANSI C language standard, or by the Neuron ® C language. A
compilation with one or more error messages results in build failure.
If you need help resolving an error, contact LonSupport; see For More
Information and Technical Support on page v.
• Fatal Errors prevent the compiler from performing any further
translation. These messages result from resource problems (out of
memory, disk full, and so on) or from internal checking on the compiler
itself. Fatal errors might also appear in the form ***TRAP n ***, where n
is a decimal number.
Traps report unexpected internal errors, and should be reported to
LonSupport; see For More Information and Technical Support on page v.
Each chapter lists the error messages in numerical order by message code. This
ordering allows for possible future minor wording changes without interfering
with your ability to locate the documentation for a particular message code.
Each error message has a category acronym and a message code. The following
message is typical:
The directive '#pragma num_alias_table_entries' is required [NCC#456]