Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error messages in ulex parsing #2

Open
Kaljurand opened this issue Mar 28, 2012 · 0 comments
Open

Improve error messages in ulex parsing #2

Kaljurand opened this issue Mar 28, 2012 · 0 comments

Comments

@Kaljurand
Copy link
Member

When loading the user lexicon, e.g. by

./ape.exe -text "" -ulexfile mylex.pl

then some syntactically incorrect lexicon entries, e.g.

noun_sg(Human, Human, neutr).
noun_sg(human being, human being, neutr).

currently result in uninformative error messages, e.g.

value="Malformed entry."
repair="User lexicon entry is malformed: noun_sg(_G1234, _G1234, neutr)"

value="Malformed file."
repair="The user lexicon file is not a valid Prolog file."
petekeller2 added a commit to petekeller2/APE that referenced this issue Sep 8, 2018
This partially addresses issue Attempto#2. Malformed file errors will display
the line number of the line that is causing the error.
Kaljurand pushed a commit that referenced this issue Sep 9, 2018
This partially addresses issue #2. Malformed file errors will display
the line number of the line that is causing the error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant