Max Brunsfeld 1e353381ff Don't create error node in lexer unless token is completely invalid ... Before, any syntax error would cause the lexer to create an error leaf node. This could happen even with a valid input, if the parse stack had split and one particular version of the parse stack failed to parse. Now, an error leaf node is only created when the lexer cannot understand part of the input stream at all. When a normal syntax error occurs, the lexer just returns a token that is outside of the expected token set, and the parser handles the unexpected token.		2016-05-26 14:15:10 -07:00
..
compiler	Distinguish separators from main tokens via a property on transitions	2016-05-19 16:27:25 -07:00
fixtures	Unify test targets, use externally defined languages as fixtures	2016-01-15 11:19:24 -08:00
helpers	Clean up lex table generation	2016-05-19 13:25:46 -07:00
integration	Avoid recompiling test languages when possible	2016-03-03 12:05:04 -08:00
runtime	Don't create error node in lexer unless token is completely invalid	2016-05-26 14:15:10 -07:00
spec_helper.h	Fix leaked lookahead trees in normal parsing	2016-01-29 17:31:43 -08:00
specs.cc	Unify test targets, use externally defined languages as fixtures	2016-01-15 11:19:24 -08:00