Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2024-02-07 | Add support for nested subscript, use for json access | Boris Kolpackov | 1 | -3/+10 | |
2024-02-07 | Add experimental support for JSON value types | Boris Kolpackov | 1 | -0/+926 | |
New types: json json_array json_object New functions: $json.value_type(<json>) $json.value_size(<json>) $json.member_{name,value}(<json-member>) $json.object_names(<json-object>) $json.array_size(<json-array>) $json.array_find(<json-array>, <json>) $json.array_find_index(<json-array>, <json>) $json.load(<path>) $json.parse(<text>) $json.serialize(<json>[, <indentation>]) For example, to load a JSON value from a file: j = $json.load($src_base/board.json) Or to construct it in a buildfile: j = [json] one@1 two@([json] 2 3 4) three@([json] x@1 y@-1) This can also be done incrementally with append/prepend: j = [json_object] j += one@1 j += two@([json] 2 3 4) j += three@([json] x@1 y@-1) Instead of using this JSON-like syntax, one can also specify valid JSON input text: j = [json] '{"one":1, "two":[2, 3, 4], "three":{"x":1, "y":-1}' Besides the above set of functions, other handy ways to access components in a JSON value are iteration and subscript. For example: for m: $j print $member_name($m) $member_value($m) print ($j[three]) A subscript can be nested: print ($j[two][1]) print ($j[three][x]) While a JSON value can be printed directly like any other value, the representation will not be pretty-printed. As a result, for complex JSON values, printing a serialized representation might be a more readable option: info $serialize($j) | |||||
2024-02-06 | Add support for value type-specific subscript and iteration | Boris Kolpackov | 1 | -18/+46 | |
2024-01-10 | Fix abs_dir_path conversion diagnostics | Boris Kolpackov | 1 | -1/+8 | |
2023-04-05 | Allow creating context with bare minimum of initializations | Boris Kolpackov | 1 | -2/+2 | |
This is used by bpkg to detect forwarded configurations without incurring the full context creation overhead. | |||||
2023-03-02 | Replace deprecated std::aligned_storage with alignas | Boris Kolpackov | 1 | -5/+5 | |
Based on patch by Matthew Krupcale. | |||||
2022-12-15 | Add noexcept to move constructors and move assignment operators | Karen Arutyunov | 1 | -1/+3 | |
2022-12-14 | Improve empty simple value to empty list of names reduction heuristics | Boris Kolpackov | 1 | -10/+31 | |
Specifically, do not reduce typed RHS empty simple values for prepend/append and additionally for assignment provided LHS is typed and is a container. | |||||
2022-10-27 | Suppress (potential) bogus GCC 12 -Wrestrict warnings | Boris Kolpackov | 1 | -3/+3 | |
2022-10-24 | Allow conversion of untyped split dir/value names to string | Boris Kolpackov | 1 | -11/+19 | |
2022-10-13 | Switch to public/private variables model | Boris Kolpackov | 1 | -1/+66 | |
Now unqualified variables are project-private and can be typified. | |||||
2022-10-11 | Factor variable patterns out of variable_pool into separate variable_patterns | Boris Kolpackov | 1 | -16/+18 | |
We have patterns only for the public variables pool. | |||||
2022-10-10 | Preparatory work for public/private variable distinction | Boris Kolpackov | 1 | -1/+95 | |
We still always use the public var_pool from context but where required, all access now goes through scope::var_pool(). | |||||
2022-10-10 | Use term shared instead of global for scope, var pool, etc | Boris Kolpackov | 1 | -7/+7 | |
2022-09-22 | Add support for hex notation for uint64 type | Boris Kolpackov | 1 | -12/+30 | |
Specifically, now we can do: x = [uint64] 0x0000ffff cxx.poptions += "-DOFFSET=$x" # -DOFFSET=65535 cxx.poptions += "-DOFFSET=$string($x, 16)" # -DOFFSET=0xffff cxx.poptions += "-DOFFSET=$string($x, 16, 8)" # -DOFFSET=0x0000ffff Note that there is no hex notation support for the int64 (signed) type. | |||||
2022-07-07 | Use new cmdline type for canned command lines in {Build,Test}script | Boris Kolpackov | 1 | -0/+132 | |
2022-06-03 | Reset value::extra on variable_map value change/version increment | Boris Kolpackov | 1 | -1/+7 | |
The reset on each modification semantics is used to implement the default value distinction as currently done in the config module but later probably will be done for ?= and $origin(). | |||||
2022-05-22 | Add support for variable patterns in config.config.disfigure | Boris Kolpackov | 1 | -0/+8 | |
2022-03-02 | Add update operation-specific variable with unmatch|match additional values | Boris Kolpackov | 1 | -1/+1 | |
Note that the unmatch (match but do not update) and match (update during match) values are only supported by certain rules (and potentially only for certain prerequisite types). Additionally: - All operation-specific variables are now checked for false as an override for the prerequisite-specific include value. In particular, this can now be used to disable a prerequisite for update, for example: ./: exe{test}: update = false - The cc::link_rule now supports the update=match value for headers and ad hoc prerequisites. In particular, this can be used to make sure all the library headers are updated before matching any of its (or dependent's) object files. | |||||
2022-01-06 | Factor reusable code to target_key::effective_name() | Boris Kolpackov | 1 | -33/+2 | |
2021-09-28 | Adapt to libbutl headers extension change from .mxx to .hxx | Karen Arutyunov | 1 | -1/+1 | |
2021-09-02 | Don't consider aliasing in variable override lookup | Boris Kolpackov | 1 | -2/+3 | |
2021-07-23 | Reserve variable names/components that start with underscore to build2 core | Boris Kolpackov | 1 | -3/+3 | |
2021-05-28 | Add support for regex-based target type/pattern specific variables | Boris Kolpackov | 1 | -14/+81 | |
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 | Ban conversion of patterns to values | Boris Kolpackov | 1 | -47/+54 | |
Also improve conversion diagnostic. | |||||
2021-05-28 | Tie loose ends in target type/pattern-specific matching | Boris Kolpackov | 1 | -5/+56 | |
2021-05-28 | Make notion of name pattern explicit, fix various related loose ends | Boris Kolpackov | 1 | -2/+1 | |
2021-04-20 | Detect environment changes in ad hoc recipes | Boris Kolpackov | 1 | -3/+24 | |
2021-04-04 | Add base functionality for hermetic build configurationshermetic | Boris Kolpackov | 1 | -0/+8 | |
2021-02-09 | Minor simplification | Boris Kolpackov | 1 | -2/+2 | |
2021-01-30 | Add std::{map, multimap} to types.hxx | Boris Kolpackov | 1 | -5/+5 | |
Seeing that std::map is becoming a common Buildfile variable type. | |||||
2021-01-28 | Make std::map prepend (=+) overriding (like insert_or_assign()) | Boris Kolpackov | 1 | -0/+6 | |
2021-01-22 | Add support for optional pair halves in variable values | Boris Kolpackov | 1 | -0/+12 | |
2020-11-11 | Make value_traits<bool>::convert() non-modifying | Boris Kolpackov | 1 | -1/+1 | |
2020-08-24 | Add copying version of convert<T>(value) | Boris Kolpackov | 1 | -0/+18 | |
2020-08-12 | Add int64 and int64s variable types | Boris Kolpackov | 1 | -0/+49 | |
2020-06-09 | Make metadata variable prefix mandatory | Boris Kolpackov | 1 | -4/+1 | |
While we could automatically set it if the target is imported, there is nothing we can do if the target is used in the same project. So to avoid confusion we make it mandatory. | |||||
2020-06-03 | Fix $process.run() to properly handle proces_path_ex | Karen Arutyunov | 1 | -1/+14 | |
2020-06-03 | Allow process path values and targets as buildscript program names | Karen Arutyunov | 1 | -0/+2 | |
Also deduce the recipe name. | |||||
2020-06-02 | Add process_path_ex with program stable name and checksum | Boris Kolpackov | 1 | -25/+197 | |
2020-06-01 | Extend target metadata to include variable prefix, stable name | Boris Kolpackov | 1 | -0/+3 | |
2020-05-27 | Add support for value subscript after expansions | Boris Kolpackov | 1 | -1/+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($y)[$z]) | |||||
2020-03-31 | Switch to project variable visibility by default | Boris Kolpackov | 1 | -8/+35 | |
2020-03-18 | Cleanup variable type/visibility/overridability logic | Boris Kolpackov | 1 | -17/+17 | |
2020-03-18 | Fix variable pattern merging logic | Boris Kolpackov | 1 | -12/+31 | |
2020-03-18 | Add $visibility(<variable>) function for querying variable visibility | Boris Kolpackov | 1 | -9/+9 | |
2020-03-17 | Rename all find*(variable) to lookup*(variable) | Boris Kolpackov | 1 | -4/+4 | |
Now we consistently use term "lookup" for variable value lookup. At some point we should also rename type lookup to binding and get rid of all the lookup_type aliases. | |||||
2020-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
2019-11-12 | Add support for vector<pair<K, V>> variable values | Boris Kolpackov | 1 | -1/+5 | |
2019-10-22 | Rename global_mutex_shards to global_mutexes | Boris Kolpackov | 1 | -2/+2 | |