diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2018-02-08 09:18:25 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2018-02-08 09:18:25 +0200 |
| commit | 6883355bc8291d740e4c86c3e15b61f227977fd1 (patch) | |
| tree | 99ac90a80845dc31a6d4d4f3bfd7462298664140 /build2/test | |
| parent | 968d8a7acd6c23078a3ea6936c03be0b45523227 (diff) | |
Update/cleanup comment documentation for inner/outer operation semantics
Diffstat (limited to 'build2/test')
| -rw-r--r-- | build2/test/rule.cxx | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/build2/test/rule.cxx b/build2/test/rule.cxx index a42ceca..7f6a133 100644 --- a/build2/test/rule.cxx +++ b/build2/test/rule.cxx @@ -35,8 +35,8 @@ namespace build2 recipe rule:: apply (action a, target& t) const { - // Note that we are called both as the outer part during the "update for - // test" pre-operation and as the inner part during the test operation + // Note that we are called both as the outer part during the update-for- + // test pre-operation and as the inner part during the test operation // itself. // // In both cases we first determine if the target is testable and return @@ -52,7 +52,7 @@ namespace build2 // // test'able | pass'able | neither // | | - // update for test delegate (& pass) | pass | noop + // update-for-test delegate (& pass) | pass | noop // ---------------------------------------+-------------+--------- // test test (& pass) | pass | noop // @@ -150,7 +150,7 @@ namespace build2 // execute them relying on update to assign their paths. // // Causing update for test inputs/scripts is tricky: we cannot - // match for update_for_install because this same rule will match + // match for update-for-install because this same rule will match // and since the target is not testable, it will return the noop // recipe. // @@ -160,7 +160,7 @@ namespace build2 // iffy, it does make sense: the outer rule we would have matched // would have simply delegated to the inner so we might as well // take a shortcut. The only potential drawback of this approach - // is that we won't be able to provide any for_test customizations + // is that we won't be able to provide any for-test customizations // when updating test inputs/scripts. But such a need seems rather // far fetched. // |