previous next contents
Error messages and warnings should be self-explanatory. Thus, this is just a list argmented with some hints.
Some of the errors will be displayed together with the name of the respective entity.
Translation time error messages contain an error position, too. It consists of the source identification
("NoName" is a window or viewer) and the character position. Due to the backtracking technique this
position is sometimes in front of the erronous construct.
Runtime error messages contain the name of the currently active rule.
Unexpected end of source- Parser expects more input.
Missing branch point- Internal translator error
Hint: this is most probrably due to an error in self-programmed terminal procedures
Type mismatch-
Invalid parameter(s)- Invalid number resp. type of parameters (checked
only for intrinsic procedures)
Syntax error- This is the standard message, if no further
analysis has performed
Unable to open file- A source file could not be opened
End-of-text exceeded- Parser expects more input.
Comment not closed- Comment opened but not closed until end of source.
Global not declared- A rule was called, which specifies a global
variable that has not been declared before, i.e. there is no memory assigned for.
Missing implementation in module- hint: Look for spelling errors.
This is also displayed if the module could not be loaded for any reasons.
Case control out of range- Number of branches does not match the branch
index
Hint: Check for nested alternatives.
.. has different type-
: FLEX index <=0 (changed to 1) -
Undefined target used-
Undeclared identifier-
Multiply defined identifier-
Identifier does not match module name- identifier following the END is
differnet from that in the module head
";" missing-
Default "N" used more than once- (Warning) There is more than one
{} construct with default control - may have unexpected results
Default "O" used more than once- (Warning) There is more than one
[] construct with default control
Default "c" used more than once- (Warning) There is more than one
(...|...|) construct with default control - the most dangerous case
Missing target specification-
Number too large-
Too many comment types defined- Maximal four comment formats can
be active simultanously.
No comment type left to remove- Illelgal invocation of DefCom('$- $','')
Illegal character in number-
SOURCETEXT across From or Back- SOURCETEXT covers a text stretch
across multiple inclusions so that it cannot be reconstructed
Illegal character in string-
not available - implementation restriction-
previous next contents
© J. Lampe 1997-2002
juergen_lampe@firemail.de
(08-May-2002)