From 721835d4dd0fe306e4b55d425f9360fac592eace Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Sun, 3 Dec 2017 13:58:28 +0200 Subject: 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. --- build2/variable.hxx | 2 -- 1 file changed, 2 deletions(-) (limited to 'build2/variable.hxx') diff --git a/build2/variable.hxx b/build2/variable.hxx index f3eea63..60a1699 100644 --- a/build2/variable.hxx +++ b/build2/variable.hxx @@ -123,7 +123,6 @@ namespace build2 const value_type* type; // If NULL, then not (yet) typed. unique_ptr override; variable_visibility visibility; - size_t generation; // load_generation of this variable. }; inline bool @@ -1070,7 +1069,6 @@ namespace build2 using value::operator=; size_t version = 0; // Incremented on each modification (variable_cache). - size_t generation; // load_generation of this value (global state only). }; using map_type = butl::prefix_map, -- cgit v1.1