aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/test/script/lexer.cxx
AgeCommit message (Collapse)AuthorFilesLines
2020-05-27Add support for value subscript after expansionsadhoc-recipe-historyBoris Kolpackov1-8/+7
Value subscript is only recognized in evaluation contexts (due to ambiguity with wildcard patterns; consider: $x[123].txt) and should be unseparated from the previous token. For example: x = ($y[1]) x = (($f ? $y : $z)[1]) x = ($identity($x)[$z])
2020-05-27Add script command redirect aliasesKaren Arutyunov1-1/+9
2020-05-27Factor out generic script parsing/executing functionality from ↵Karen Arutyunov1-218/+19
build2::test::script namespace
2020-05-27Handle multi-curly-brace tokens in lexerBoris Kolpackov1-1/+1
2020-05-27Add lexer mode dataBoris Kolpackov1-2/+2
2020-05-27Add recognition for line-leading `%` as tokenBoris Kolpackov1-1/+1
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2019-11-15Generalize attributes to be comma-separated with arbitrary valuesBoris Kolpackov1-1/+1
Before: x = [string null] After: x = [string, null]
2019-11-14Tighten up attribute recognition during parsingBoris Kolpackov1-22/+26
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-07-05Move config, dist, test, and install modules into libraryKaren Arutyunov1-0/+551