parrot/parrot — Issue #198: ops2c has abysmal parse error messages
Author: moritz
Created: 2011-11-12 10:26:55+00:00
State: open

When ops2c doesn't understand the body of a dynop, it produces this error message:

Fail to parse op body at line 174, near "{\n mp_i"

so it complains not about a particular line, but about the whole body of the op. This is very frustrating when writing a dynop of more than two lines, because it tells me nothing about the actual error.

ops2c needs to report errors at least at statement granularity for it to be useful to the developer.