diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2020-04-28 07:29:11 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2020-04-30 14:44:21 +0200 |
commit | 9498585efc6e92eabca596d2ecbb78ffb343bca2 (patch) | |
tree | 6cee37adc289643e37f7c5827490669a6e9e1dda /libbuild2/action.hxx | |
parent | 68cc1badd2eb96fd1f89e8b6519d45039ff983ba (diff) |
Factor recipe to separate header/source files
Diffstat (limited to 'libbuild2/action.hxx')
-rw-r--r-- | libbuild2/action.hxx | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/libbuild2/action.hxx b/libbuild2/action.hxx index ec2701f..c1e4697 100644 --- a/libbuild2/action.hxx +++ b/libbuild2/action.hxx @@ -40,9 +40,10 @@ namespace build2 // it via rule/recipe override but that didn't end up well, to put it // mildly). While the outer operation normally "directs" the inner, inner // rules can still be matched/executed directly, without outer's involvement - // (e.g., because of other inner rules). A typical implementation of an - // outer rule either returns noop or delegates to the inner rule. In - // particular, it should not replace or override the inner's logic. + // (e.g., because of dependencies in other inner rules). A typical + // implementation of an outer rule either returns noop or delegates to the + // inner rule. In particular, it should not replace or override the inner's + // logic. // // While most of the relevant target state is duplicated, certain things are // shared among the inner/outer rules, such as the target data pad and the |