MESSAGES - diagnostic messages generated by NSC.
The NSC compiler can generate several different classes of diagnostic messages.
Each class is identified by a label such as "Warning" or "Fatal Error".
The list below explains each such error.
- Unlabelled (just a diagnostic message)
- If a diagnostic message has no identifying label, the compiler
has found an error serious enough to prevent generating code.
The compiler will continue to parse the source input and look for
additional problems, but no code will be generated.
- Warning
- The compiler has found an error that means the source code
is incorrect, but the compiler will generate source code anyway.
A typical example is an #include directive that's
missing the name of the file you want to include.
The compiler can continue parsing and will generate code as if the
#include directive wasn't there; however, your program is
probably in trouble and more errors will occur.
- Unusual
- The compiler has found a construct that is valid but so unusual it's probably incorrect.
For example,
while(1) ;
is valid C code, but a guaranteed infinite loop and therefore worthy of comment.
- Note
- The compiler has found a construct that is strictly illegal, but will usually work anyway.
A typical example is specifying "%d" in a "printf" format string
when the corresponding argument is a long. This violates the rules of ANSI C,
but will usually work, since long is the same length as int in
many C implementations. The compiler will continue parsing and will generate code if no other
errors are found.
- Fatal Error
- The compiler has found a construct that prevents any further parsing. No code will be generated.
The most common fatal error is simply getting too many other types of errors—past a point,
the compiler assumes the program is so erroneous that going farther is a waste of time.
- Internal Error
- The compiler found itself in an invalid state (for example, the compiler's internal data structures
were found to be corrupted). Please save a copy of the source code that caused the problem and
contact GCOS8 Technical Support.
- Machine Dependency
- The compiler found a construct which was strictly legal but which will behave differently
on different systems. For example, this message is issued if you use a bit-field to hold a pointer.
Copyright © 2003, Thinkage Ltd.