aboutsummaryrefslogtreecommitdiff
path: root/build2/cc/link-rule.cxx
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2018-02-08 09:18:25 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2018-02-08 09:18:25 +0200
commit6883355bc8291d740e4c86c3e15b61f227977fd1 (patch)
tree99ac90a80845dc31a6d4d4f3bfd7462298664140 /build2/cc/link-rule.cxx
parent968d8a7acd6c23078a3ea6936c03be0b45523227 (diff)
Update/cleanup comment documentation for inner/outer operation semantics
Diffstat (limited to 'build2/cc/link-rule.cxx')
-rw-r--r--build2/cc/link-rule.cxx4
1 files changed, 2 insertions, 2 deletions
diff --git a/build2/cc/link-rule.cxx b/build2/cc/link-rule.cxx
index b6b707d..cd355c6 100644
--- a/build2/cc/link-rule.cxx
+++ b/build2/cc/link-rule.cxx
@@ -290,7 +290,7 @@ namespace build2
file& t (xt.as<file> ());
- // Note that for_install is signalled by install_rule and therefore
+ // Note that for-install is signalled by install_rule and therefore
// can only be relied upon during execute.
//
match_data& md (t.data (match_data ()));
@@ -449,7 +449,7 @@ namespace build2
//
// Note that we do it here regardless of whether we are installing
// or not for two reasons. Firstly, it is not easy to detect this
- // situation in apply() since the for_install hasn't yet been
+ // situation in apply() since the for-install hasn't yet been
// communicated by install_rule. Secondly, always having the member
// takes care of cleanup automagically. The actual generation
// happens in perform_update() below.