Keil Software — A51/AX51/A251 Macro Assembler and Utilities |
193 |
|
|
MACRO Errors
The MPL processor emits error messages if errors occur in the MPL processing phase. Macro errors are displayed like other assembly errors in the listing file. The following table lists the error messages generated by the MPL processor.
Number |
Error Message and Description |
|
|
200PREMATURE END OF FILE
The end of the source module was reached while processing some macro call, which requires more input from the source file.
201'<token>' IDENTIFIER EXPECTED
The MPL processor expected an identifier while processing some macro. None was found. The unexpected token is displayed with this error message.
202MPL FUNCTION '<name>': '<character>' EXPECTED
The context of the MPL processor language requires a specific character from the input given by <character> while processing the built-in function given by <name>.
203<string>: UNBALANCED PARENTHESES
A balanced string requires the same number of right parentheses and left parentheses.
204EXPECTED '<token>'
The syntax requires a specific token to follow, for example THEN after the balanced text argument to IF.
205INCOMPLETE MACRO DEFINITION
The macro definition has not been completely processed due to premature end of input file.
206FUNCTION 'MATCH': ILLEGAL CALL PATTERN
|
The built-in function MATCH was called with an illegal call pattern. The call pattern |
6 |
|
must consist of some formal name followed by a delimiter specification and another |
|
|
formal name. |
|
207 |
FUNCTION 'EXIT' IN BAD CONTEXT |
|
|
The built-in function EXIT is allowed only in the loop control constructs WHILE and |
|
|
|
|
|
REPEAT. |
|
|
|
|
208 |
ILLEGAL METACHARACTER '<character>' |
|
|
The first character of the balanced text argument to METACHAR is taken to be the |
|
|
new value of the metacharacter. The characters @, (, ), *, blank, tab, and |
|
|
identifier-characters are not allowed to be the metacharacter. |
|
209 |
CALL PATTERN - DELIMITER '<delimiter>' NOT FOUND |
|
|
The call pattern of some macro does not conform to the define pattern of that macro. |
|
|
The delimiters of the macro call should be checked for conformance. |
|
|
|
|
210 |
CALL TO UNDEFINED MACRO '<name>' |
|
|
The macro call specifies the name of an undefined macro. |
|
194 |
|
Chapter 6. Macro Processing Language |
|
|
|
|
|
|
|
|
|
|
Number |
Error Message and Description |
|
|
|
|
|
211INVALID MPL COMMAND '%<character>'
The character following the metacharacter does not form a valid MPL command.
212INVALID DIGIT '<character>' IN NUMBER
A number of an expression contains an invalid digit.
213UNCLOSED STRING OR CHARACTER CONSTANT
214INVALID STRING OR CHARACTER CONSTANT
The string representing a number in an expression is invalid. The string must be either one or two characters long. A character constant must not be longer than one character. Strings or character constants must be enclosed by single or double quotes.
215UNKNOWN EXPRESSION IDENTIFIER
The identifier within some expression is not an operator or a number.
216<character>: INVALID EXPRESSION TOKEN
The given character does not form a valid operator or an identifier operator.
217DIV/MOD BY ZERO
A division or modulo by zero error occurred while evaluating an expression.
218EVAL: SYNTAX ERROR IN EXPRESSION
The expression to be evaluated contains a syntax error, for example two consecutive number, not separated by an operator.
219CAN'T OPEN FILE '<file>'
The file specified in the INCLUDE directive could not be opened.
220'<file>' IS NOT A DISK FILE
The file name given in the INCLUDE directive does not specify a disk file. Files other than disk files are not allowed (example: CON).
221ERROR IN INCLUDE DIRECTIVE
6 |
The INCLUDE directive is ill-formed. The argument to INCLUDE must be the name |
|
of some file, enclosed in parentheses. |
||
|
||
|
|