Rule doesn't match

I develop a pascal-like language and one of my rule doesn't work. terminals { INTEGER -> [0-9]+ } rules { constant -> INTEGER ; subrange -> INTEGER '..' INTEGER ; case_statem...

Id #499 | Release: None | Updated: Oct 22, 2014 at 7:04 PM by kep4uk | Created: Oct 22, 2014 at 6:59 PM by kep4uk

Symbol.Name not as specified in terminals

When we have a specified terminal, for example: ASSIGN -> ':=' ; and any from own rules contains a direct terminal expression, for example: statement -> variable ASSIGN expression; statement2 -> ...

Id #498 | Release: None | Updated: Oct 22, 2014 at 12:36 PM by kep4uk | Created: Oct 21, 2014 at 6:48 PM by kep4uk

Semantic actions executed before tree actions

The semantic actions are called before all the internal tree actions have been executed (the replacing of the auto-generated intermediate nodes). Hence the body symbols of the semantic actions do n...

Id #497 | Release: Hime Parser Generator v0.6.1 | Updated: Feb 24, 2014 at 6:41 AM by lwouters | Created: Feb 24, 2014 at 6:41 AM by lwouters

Enable parser halting on first error (no recovery)

Currently, the intended parser's behaviour is to recover from errors. This behaviour should be open to definition by the user to enable parser's halting as soon as an error is encountered.

Id #496 | Release: Hime Parser Generator v1.0.0 | Updated: Feb 24, 2014 at 6:48 AM by lwouters | Created: Oct 22, 2011 at 8:21 AM by lwouters

Merge lexical and syntactic error reporting in generated parsers

Lexical errors are reported in the lexer's Errors property and the syntactic errors are reported in the parser's Errors property. It would be more natural to users to have only one source of errors...

Id #495 | Release: None | Updated: Oct 22, 2011 at 9:32 AM by lwouters | Created: Oct 22, 2011 at 8:17 AM by lwouters

Bug in lexer

Bug causing the lexer to not rewiding correctly the input on matching tokens shorter than expected.

Id #494 | Release: None | Updated: Oct 21, 2011 at 5:11 PM by lwouters | Created: Oct 21, 2011 at 4:43 PM by lwouters

Generated parser not halting on incorrect input?

I have been attempting to use Hime to generate a parser for a subset of C++. In doing so, I have stumbled across behavior I didn't expect and which seems like a bug to me (admittedly my experience ...

Id #485 | Release: Hime Parser Generator v1.0.0 | Updated: Feb 24, 2014 at 6:49 AM by lwouters | Created: Oct 18, 2011 at 3:34 AM by joshpetrie

what are the possible options?

Is there a list of possible options somewhere in the documentation? Thanx.

Id #437 | Release: None | Updated: Sep 14, 2011 at 12:27 PM by lwouters | Created: Aug 6, 2011 at 5:03 PM by hymans

Give line number for error

When doing himecc on an empty file, there is an error. But no line number is given for the error. It would be nice to have this piece of information.

Id #435 | Release: None | Updated: Oct 22, 2011 at 9:31 AM by lwouters | Created: Aug 2, 2011 at 4:54 PM by hymans

Options -log and -doc do not seem to be working

even though -l and -d do.

Id #420 | Release: None | Updated: Sep 14, 2011 at 12:05 PM by lwouters | Created: Jul 17, 2011 at 7:52 AM by hymans