aboutsummaryrefslogtreecommitdiff
path: root/build2/cc/types.hxx
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2019-05-03 13:23:33 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2019-05-03 13:23:33 +0200
commit8618078b90189fb49e9c0a76ac01d471b51f1e93 (patch)
tree63ee0435f3311d90d5863ca49a3dc0e5807bb097 /build2/cc/types.hxx
parent43c53a8b475f901a902ba1bf6ec603e7a28311b1 (diff)
Rename [config.]cxx.header_units to importable_headers
Diffstat (limited to 'build2/cc/types.hxx')
-rw-r--r--build2/cc/types.hxx7
1 files changed, 6 insertions, 1 deletions
diff --git a/build2/cc/types.hxx b/build2/cc/types.hxx
index 4403e4c..60c9a34 100644
--- a/build2/cc/types.hxx
+++ b/build2/cc/types.hxx
@@ -21,7 +21,12 @@ namespace build2
//
// Note that our terminology doesn't exactly align with the (current)
// standard where a header unit is not a module (that is, you either
- // import a module unit or a header unit).
+ // import a "module [interface translation unit]" or a "[synthesized]
+ // header [translation] unit"). On the other hand, lots of the underlying
+ // mechanics suggest that a header unit is module-like; they end up having
+ // BMIs (which stand for "binary module interface"), etc. In a sense, a
+ // header unit is an "interface unit" for (a part of) the global module
+ // (maybe a partition).
//
enum class unit_type
{