Bad recoveries like the one in Spoofax/168 can lead to large skipped regions. Especially now with keyword highlighting it may not be obvious that at the end of the region there may be a parse error that causes it not to be parsed. Maybe for large, >20 line regions we should mark the entire region as erroneous? Or maybe add a special error marker at the first line of the region, saying something like “region could not be parsed because of subsequent syntax errors (see below)”?

Submitted by Lennart Kats on 11 June 2010 at 13:22

On 14 June 2010 at 12:24 Lennart Kats commented:

Implemented in 0.5.1.

On 14 June 2010 at 17:25 Lennart Kats closed this issue.

Log in to post comments