Databases
StackOverflow2013
Postsdbo
POANTLR: how to extract error messages when build fails
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POANTLR: how to extract error messages when build fails
    primarykey
    data
    text
    <p>I've built my lexer and parser in ANTLR and they work really well in the sense that when user code fails to parse, it outputs useful error messages to STDERR, showing the exact line no. etc. </p> <p>The problem is, I need to extract this information in order to display the error messages in my Eclipse editor at the correct positions, but it doesn't seem to be available anywhere except on STDERR. I'm basically looking for some kind of myParser.getErrorMessages().</p> <p>Has anybody come across a solution to this?</p> <p>I found the below link, however this only works if the user code partially parses (i.e. so we still get an AST). When it fails completely, you don't get a tree back. <a href="http://tech.puredanger.com/2007/02/01/recovering-line-and-column-numbers-in-your-antlr-ast/" rel="nofollow">http://tech.puredanger.com/2007/02/01/recovering-line-and-column-numbers-in-your-antlr-ast/</a></p> <p>I also found this exact question in the official ANTLR FAQ... but I really don't understand his solution. Can anybody translate it for me? I'm not using any of the classes he refers to, and he's talking about v4 (which isn't released yet). <a href="http://www.antlr.org/wiki/display/ANTLR3/Pattern+for+returning+errors+from+ANTLR+in+data+structures%2C+not+STDERR" rel="nofollow">http://www.antlr.org/wiki/display/ANTLR3/Pattern+for+returning+errors+from+ANTLR+in+data+structures%2C+not+STDERR</a></p> <p>My code looks as follows:</p> <pre><code>FileInputStream fis = new FileInputStream("UserCode.txt"); ANTLRInputStream input = new ANTLRInputStream(fis); MyLexer lexer = new MyLexer(input); CommonTokenStream tokens = new CommonTokenStream(lexer); MyParser parser = new MyParser(tokens); CommonTree tree = (CommonTree)parser.flow().getTree(); MyAST ast = new MyAST(tree); </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USTom G
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COSee: http://www.antlr.org/wiki/display/ANTLR3/Error+reporting+and+recovery (not sure if the examples are fully compatible with ANTLR v3.2/v3.3, but if not, there shouldn't be too many changes to get it working)
      singulars
      1. POANTLR: how to extract error messages when build fails
      1. USBart Kiers
    2. COThis answers my question. Thanks Bart!
      singulars
      1. POANTLR: how to extract error messages when build fails
      1. USTom G
    3. COyou're welcome.
      singulars
      1. POANTLR: how to extract error messages when build fails
      1. USBart Kiers
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload