BAP Online Manuals : Compiler Reference Manual : Appendix : Compiler Error Messages
Previous: Compiler Restrictions
Next: Compiler Example

---

3.6.2. Compiler Error Messages

Most error messages will explain themselves sufficiently. The message you will probably most often see is the ' ERROR in body: ' message. This simply means that the parser was not able to parse a term from the point that is indicated until the next dot character or keyword. Common mistakes that trigger this messages are unbalanced parenthesis as well as missing conjunctions or ',' in front of a closing bracket.

We are sorry that this version is not able to give a more specific location, but a general user defined operators has a hard time to determine the exact cause of an error. We will provide a better solution with the next release of BAP.

• Couldn't access environment variable <name>.

• Couldn't find file: <filename>

• Couldn't open file: <filename>

• ERROR ';' expected instead of ','

• ERROR in Body:

• ERROR in Definition: use op(<Priority>,<XFY>,<Operator>). instead

• ERROR in defintion: use <atom> = <term>. instead

• ERROR in Domain Definition

• ERROR: Couldn't open file: <filename>

• ERROR: Interface entry is faulty

• ERROR: Keyword expected

• ERROR: Predicate <name> is already defined

• ERROR: Predicate not defined: <name>

• ERROR: Wrong number of arguments of clause <clause name>

• ERROR: Wrong spelling of functor of clause <correct name>

• FATAL: Something went wrong, scanner/parser aborted

• Illegal Token <token>

• MODULE already defined

• No MODULE definition is source

• String not terminated

• WARNING: Variable <name> only used once

---

BAP Online Manuals : Compiler Reference Manual : Appendix : Compiler Error Messages
Previous: Compiler Restrictions
Next: Compiler Example