6 Commits (917cf1cf2a85d3069e10a2d17caa19c2cfcac92a)

Author	SHA1	Message	Date
David Majda	917cf1cf2a	Start rule of the grammar is now implicitly its first rule ... Before this change, the start rule was the one named "start" and there was an option to override that. This is now impossible. The goal of this change is to contain all information for the parser generation in the grammar itself. In the future, some override directive for the start rule (like Bison's "%start") may be added to the grammar.	14 years ago
David Majda	e63f64a3d5	Make the generated parsers standalone (no runtime is required). ... This and also speeds up the benchmark suite execution by 7.83 % on V8. Detailed results (benchmark suite totals): --------------------------------- Test # Before After --------------------------------- 1 26.17 kB/s 28.16 kB/s 2 26.05 kB/s 28.16 kB/s 3 25.99 kB/s 28.10 kB/s 4 26.13 kB/s 28.11 kB/s 5 26.14 kB/s 28.07 kB/s --------------------------------- Average 26.10 kB/s 28.14 kB/s --------------------------------- Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/533.2 (KHTML, like Gecko) Chrome/5.0.342.7 Safari/533.2	14 years ago
David Majda	d3104742d9	Fixed --start vs. --start-rule inconsistency between help and actual option processing code.	14 years ago
David Majda	a43d1b33e3	Bootstrapped the grammar parser, yay! I should have done this long ago.	14 years ago
David Majda	0a5788b50e	Fixed typo in help: "parserVar" -> "parser_var".	14 years ago
David Majda	c3dd696a3e	Initial commit.	14 years ago