3 Commits

Author	SHA1	Message	Date
Martin Atkins	3c0dde2ae5	zclwrite: foundations of the writer parser ... The "writer parser" is a parser that produces a writer AST rather than a zclsyntax AST. This can be used to produce a writer AST from existing source in order to modify it before writing it out again. It's implemented with the somewhat-unintuitive approach of running the main zclsyntax parser and then mapping the source ranges it finds back onto the token sequence to pull out the raw tokens for each object. This allows us to avoid maintaining two parsers but also keeps all of this raw-token-wrangling complexity out of the main parser.	2017-06-06 08:53:13 -07:00
Martin Atkins	e100bf4723	zclsyntax: generate lexer diagnostics ... There are certain tokens that are _never_ valid, so we might as well catch them early in the Lex... functions rather than having to handle them in many different contexts within the parser. Unfortunately for now when such errors occur they tend to be echoed by more confusing errors coming from the parser, but we'll accept that for now.	2017-06-04 07:34:26 -07:00
Martin Atkins	476e2c127e	zclwrite: convert zclsyntax tokens into zclwrite tokens ... In zclwrite we throw away the absolute source position information and instead just retain the number of spaces before each token. This different model allows us to rewrite parts of the token sequence without needing to re-adjust all of the positions, and it also allows us to do simple indentation and spacing adjustments just by walking through the token list and adjusting these numbers.	2017-05-29 16:59:20 -07:00