previous         next         contents

Appendix B: Error messages

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 ("" is a window or viewer) and the character position. Due to the backtracking parser 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. (It is very likely then that it missed a closing symbol for comments or strings or something like this. Also accepting a deliminator word like 'END' as an identifier can be the reason.)
Missing branch point
Internal translator error
Hint: This is most probably 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 been 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 allocated for it.
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. Their controls may interfer.
.. has different type
: FLEX index <=0 (changed to 1)
Undefined target used
An undefined target is used. For this an error text "<***UNDEFINED TARGET***>" will be substituted.
Undeclared identifier
An identifier was not declared. This may also be a follow up of another syntax error, which caused a rule being seen as a variable.
Multiply defined identifier
Identifier does not match module name
identifier following the END is different 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
A rule name is used in an expression without trailing '_'. In fact, the reason may be a missing identifier which is accidently interpreted as a rule name.
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 an inclusions border so that it cannot be reconstructed
Illegal character in string
not available - implementation restriction
No such file
File does not exist.
    previous         next         contents

© J. Lampe 1997-2010