Parse errors are hard to debug.

Issue #6 resolved
Edd Barrett
created an issue

A typical parse error looks like this:

>?- consult(binarytrees).
RPython traceback:
  File "implement.c", line 219, in entry_point
  File "prolog_interpreter_translatedmain.c", line 213, in repl
  File "prolog_interpreter_translatedmain.c", line 1244, in run
  File "prolog_interpreter_continuation.c", line 2833, in driver
  File "implement.c", line 20054, in wrap_consult_1
  File "prolog_interpreter_parsing.c", line 1049, in parse_file
  File "rpython_rlib_parsing_parsing.c", line 3846, in PackratParser_parse

A user-readable message should be shown including a line number indicating where the parse error is.

Comments (1)

  1. Log in to comment