'(' After Control Expected
Some control parameters need an argument enclosed in parentheses.
This message is displayed when the left parenthesis is
missing.
')' After Parameter Expected
This message indicates that the right parenthesis of the enclosed
argument is missing.
'=' Expected
This message indicates a syntax error with the specified WARNING directive or pragma.
Bad Digit In Number
The numerical argument of a control parameter contains invalid
characters. Only decimal digits are acceptable.
Can't Create File
The filename defined on the FILE line cannot be created.
Can't Have General Control In Invocation Line
General controls like EJECT
cannot be included on the command line. Place these controls in the
source file using the #pragma statement.
File Does Not Exist
The filename defined on the FILE line, cannot be found.
File Write-Error
An error occurred while writing to the list, preprint, work, or
object file because of insufficient disk space.
Identifier Expected
This message is generated when the DEFINE directive has no arguments. The
DEFINE directive requires an identifier as its argument.
This is the same convention as in the C language.
Line Too Long
The maximum length of the command line may not exceed 500
characters. The same limit also applies to the contents of a
command file (@cmdfile).
Memory Space Exhausted
The compiler could not allocate enough memory to compile the
specified source file. If you receive this message consistently,
you should split the source file into two or more smaller files and
re-compile.
More Than 100 Errors in Source-File
During the compilation more than 100 errors were detected. This
causes the termination of the compiler.
Non-Null Argument Expected
The selected control parameter needs an argument (for example, a
filename or a number) enclosed in parentheses.
Numeric Value Out Of Range
The numerical argument of a control parameter is out of range. For
instance, the OPTIMIZE
directive allows only certain numbers. A value of 25 would generate
this error message.
Parse Stack Overflow/Statements Are Too Nested
The parse stack has overflowed. This can occur if the source
program contains extremely complex expressions or if blocks are
nested more than 31 levels deep.
Preprocessor: Line Too Long (32K)
An intermediate expansion exceeded 32K characters in length.
Preprocessor: Macros Too Nested
During macro expansion, the stack consumption of the preprocessor
grew too large to continue. This message usually indicates a
recursive macro definition, but can also indicate a macro with too
many levels of nesting.
Respecified Or Conflicting Control
A command-line parameter was specified twice or conflicting
command-line parameters were specified.
Source Must Come From A Disk-File
The source and include files must exist on either a hard disk or
diskette. The console CON:, :CI:, or similar devices
are not allowed as input files.
Unknown Control
The selected control parameter is not recognized by the
compiler.
This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.
ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.