diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2017-12-03 13:58:28 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2017-12-03 13:58:28 +0200 |
| commit | 721835d4dd0fe306e4b55d425f9360fac592eace (patch) | |
| tree | c6358c198a444d2ce387942e17e22c8bac7f55b7 /build2/scope.hxx | |
| parent | c49b0e8ca53928cc20e9d4832536baaeee6d7a9d (diff) | |
Allow typification of variables and values across load generations
The original semantics turned out to be too restrictive. For example, the
user may have specified the config.c variable on the command line that is
only used by an imported project that is loaded in a subsequent generation.
We are also relaxing it for values since conceptually the two feel the same.
For a value the (hypothetical) example is a "common" variable set in a project
root that is only queried in a subdirectory in a subsequent generation.
Diffstat (limited to 'build2/scope.hxx')
| -rw-r--r-- | build2/scope.hxx | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/build2/scope.hxx b/build2/scope.hxx index 00aba52..5d0fcd8 100644 --- a/build2/scope.hxx +++ b/build2/scope.hxx @@ -316,7 +316,7 @@ namespace build2 // Temporary scope. The idea is to be able to create a temporary scope in // order not to change the variables in the current scope. Such a scope is // not entered in to the scope map. As a result it can only be used as a - // temporary set of variables. In particular, defining targetsdirectly in + // temporary set of variables. In particular, defining targets directly in // such a scope will surely end up badly. Defining any nested scopes will be // as if defining such a scope in the parent (since path() returns parent's // path). |