Jan Moringen
Jan Moringen
Hi, note that the esrap repository from which quicklisp fetches is scymtym/esrap. Regarding your question: I have been working on parse error reports like ``` At t a { a...
OK, the code will need some work before it can go into master, but I will try to get it done as soon as possible.
@dimitri, I pushed a draft of the improved parse error reporting to scymtym/esrap:wip-better-errors. In addition to the error position, parse errors report - the most specific rule that failed to...
> Could you please try removing a comma separator in the file (I tested just after the truncate keyword), or maybe removing the d letter from the “enclosed” keyword, etc,...
I will try to clean up and merge the code as quickly as I can. No promises though.
@dimitri Just to keep you informed: most of the improved error reporting code is approaching acceptable quality with tests and all. However, there is one design decision (scraping the required...
A much improved version of this code is in https://github.com/scymtym/esrap master (which is the maintained upstream repository)
> > I think they must have been compiling let2.lisp, > The backtrace mentions let1.lisp. maybe they added the variable manually and forgot to update the file name. Yes, I...
I was bitten by the same issue for `quicklisp-client:who-depends-on`.
Rebased for master changes.