aboutsummaryrefslogtreecommitdiff
path: root/build2
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2019-05-15 08:50:28 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2019-05-15 08:50:28 +0200
commitfbc9a384e013fdb38b56f42e3850915474cb5785 (patch)
tree76b0a3fc5f863b90c27a552625b7a19c79eaefb9 /build2
parenta6c6186d18c928a2358796442f01903895b67677 (diff)
Update ad hoc group semantics comment to reflect new functionality
Diffstat (limited to 'build2')
-rw-r--r--build2/target.hxx22
1 files changed, 13 insertions, 9 deletions
diff --git a/build2/target.hxx b/build2/target.hxx
index 61fe111..b389ea5 100644
--- a/build2/target.hxx
+++ b/build2/target.hxx
@@ -216,20 +216,24 @@ namespace build2
// proper targets.
//
// So to support this requirement we have "ad hoc" groups. The idea is
- // that any target can be turned (by the rule that matched it) into an ad
- // hoc group by chaining several targets. Ad hoc groups have a more
- // restricted semantics compared to the normal groups. In particular:
+ // that any target can be turned either by a user's declaration in a
+ // buildfile or by the rule that matches it into an ad hoc group by
+ // chaining several targets together.
+ //
+ // Ad hoc groups have a more restricted semantics compared to the normal
+ // groups. In particular:
//
// - The ad hoc group itself is in a sense its first/primary target.
//
- // - Group member's recipes should be set to group_recipe by the group's
- // rule.
+ // - Group member's recipes, if set, should be group_recipe. Normally, a
+ // rule-managed member isn't matched by the rule since all that's
+ // usually needed is to derive its path.
//
- // - Members are discovered lazily, they are only known after the group's
- // rule's apply() call.
+ // - Unless declared, members are discovered lazily, they are only known
+ // after the group's rule's apply() call.
//
- // - Members cannot be used as prerequisites but can be used as targets
- // - (e.g., to set variables, etc).
+ // - Only declared members can be used as prerequisites but all can be
+ // used as targets (e.g., to set variables, etc).
//
// - Members don't have prerequisites.
//