summaryrefslogtreecommitdiffstats
path: root/src/lexer.in.cc
Commit message (Collapse)AuthorAgeFilesLines
* allow UTF-8 in rule descriptionsEvan Martin2012-04-261-1/+1
| | | | | The lexer already mostly allowed this, except that chars >127 were being interpreted as negative indexes into the lexer table.
* parse $:Peter Kuemmel2012-01-291-0/+20
| | | | | '$:' is a valid string now, it expands to ':' update error messages and show a hint when something went wrong.
* add colon escapingPeter Kuemmel2012-01-291-0/+4
| | | | | | | | Needed for Windows drive names. For instance configure with gtest: python configure.py --with-gtest=c$:\gtest-1.6.0
* Merge pull request #194 from evanj/newline_spacesEvan Martin2012-01-051-1/+1
|\ | | | | Lexer: include leading spaces in the newline token.
| * Lexer: include leading spaces in the newline token.Evan Jones2012-01-051-1/+1
| | | | | | | | This means that indented blank lines are skipped without causing errors.
* | Lexer: Remove the trailing newline from lexer.in.cc not just lexer.ccEvan Jones2012-01-051-1/+1
|/ | | | This probably should have been part of commit eeed7241
* Lexer: include leading whitespace in the comment token.Evan Jones2012-01-051-1/+1
| | | | Indented comments are ignored rather than causing errors.
* windows: more build fixesScott Graham2012-01-041-0/+1
|
* allow hyphen in variable namesEvan Martin2011-12-301-2/+2
|
* make evalstring internals privateEvan Martin2011-12-301-6/+6
|
* build fixEvan Martin2011-12-301-0/+2
|
* switch the core ninja parser to use re2c for the lexerEvan Martin2011-12-291-0/+234
- Delete the old "Tokenizer" code. - Write separate tests for the lexer distinct from the parser. - Switch the parser to use the new code. - New lexer error output has file:line numbers so e.g. Emacs can jump your editor to the syntax error. - The EvalEnv ($-interpolation) code is now part of the lexer as well.