Repository: mesos Updated Branches: refs/heads/master c250c0625 -> 4b649e7ec
Clarified the style guide on namespace aliases. Project: http://git-wip-us.apache.org/repos/asf/mesos/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/4b649e7e Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/4b649e7e Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/4b649e7e Branch: refs/heads/master Commit: 4b649e7ec3a78973471edc378f516a2a6b8122ce Parents: c250c06 Author: Benjamin Mahler <[email protected]> Authored: Tue Sep 29 17:01:45 2015 -0700 Committer: Benjamin Mahler <[email protected]> Committed: Tue Sep 29 17:01:45 2015 -0700 ---------------------------------------------------------------------- docs/mesos-c++-style-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos/blob/4b649e7e/docs/mesos-c++-style-guide.md ---------------------------------------------------------------------- diff --git a/docs/mesos-c++-style-guide.md b/docs/mesos-c++-style-guide.md index 02f4dc9..d218aab 100644 --- a/docs/mesos-c++-style-guide.md +++ b/docs/mesos-c++-style-guide.md @@ -10,7 +10,7 @@ The Mesos codebase follows the [Google C++ Style Guide](http://google-styleguide ### Namespaces * We avoid `using namespace foo` statements as it is not explicit about which symbols are pulled in, and it can often pull in a lot of symbols, which sometimes lead to conflicts. -* We suggest using namespace aliases to help pull in sub namespaces, such as `namespace bar = foo::bar;`; or using the full sub namespaces, such as `using namespace foo::bar;` where `bar` is the exact symbol you want to use. These should only be present at the top of the .cpp file. +* It is OK to use namespace aliases to help pull in sub-namespaces, such as `namespace http = process::http;`. These should only be present at the top of the .cpp file. ## Naming
