Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2021-05-28 | Add support for regex-based target type/pattern specific variables | Boris Kolpackov | 1 | -1/+2 | |
This is in addition to the already supported path-based target type/pattern specific variables. For example: hxx{*}: x = y # path-based hxx{~/.*/}: x = y # regex-based | |||||
2021-05-28 | Recognize quoting of first character in token | Boris Kolpackov | 1 | -7/+18 | |
Use this to relax the pattern inclusion/exclusion syntax to only require unquoted +/-. | |||||
2020-07-13 | Reserve backtick (`) and bit-or (|) in eval context for future use | Boris Kolpackov | 1 | -0/+1 | |
Specifically, they are reserved for future support of arithmetic evaluation contexts and evaluation pipelines, respectively. | |||||
2020-06-10 | Handle special variable names when spelled as $(<char>) rather than $<char> | Boris Kolpackov | 1 | -0/+1 | |
2020-05-27 | Initial support for ad hoc recipes (still work in progress) | Boris Kolpackov | 1 | -5/+43 | |
2020-03-20 | Lexer support for default value assignment (?=) | Boris Kolpackov | 1 | -0/+1 | |
Note: not yet supported in the parser. | |||||
2020-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
2019-11-14 | Tighten up attribute recognition during parsing | Boris Kolpackov | 1 | -2/+7 | |
Now it should be possible to use `[]` for wildcard patterns, for example: foo = foo.[hit]xx Note that a leading bracket expression will still be recognized as attributes and escaping or quoting it will inhibit pattern matching. To resolve this case we need to specify an empty attribute list: foo = [] [abc]-foo.cxx | |||||
2019-11-11 | Use path_name for `-` to stdin/stdout translation | Karen Arutyunov | 1 | -7/+7 | |
2019-09-30 | Add support for `case` pattern alternatives | Boris Kolpackov | 1 | -0/+2 | |
case <pattern>[ | <pattern>...] | |||||
2019-07-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+191 | |