Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarifying namespace using #845

Open
wants to merge 4 commits into
base: gh-pages
Choose a base branch
from
Open

Clarifying namespace using #845

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0f12760
clarifying case senstivity in include order
ArvindReddySheelam Jul 19, 2024
e635540
clarifying case sensitivity in include order
ArvindReddySheelam Jul 19, 2024
a164d25
clarifying case sensitivity in include oreder
ArvindReddySheelam Jul 19, 2024
0a054fc
Clarifying the usage of 'using namespace' directives and 'using' decl…
ArvindReddySheelam Jul 28, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 27 additions & 6 deletions cppguide.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -399,8 +399,8 @@ <h3 id="Names_and_Order_of_Includes">Names and Order of Includes</h3>
<p>Include headers in the following order: Related header, C system headers,
C++ standard library headers,
other libraries' headers, your project's
headers.</p>

headers.
The includes should be ordered alphabetically. This ordering should be case-sensitive, meaningthat uppercase and lowercase letters are considered to be different</p>
<p>
All of a project's header files should be
listed as descendants of the project's source
Expand Down Expand Up @@ -498,7 +498,6 @@ <h3 id="Names_and_Order_of_Includes">Names and Order of Includes</h3>

#include &lt;string&gt;
#include &lt;vector&gt;

#include "base/basictypes.h"
#include "foo/server/bar.h"
#include "third_party/absl/flags/flag.h"
Expand Down Expand Up @@ -526,12 +525,34 @@ <h3 id="Namespaces">Namespaces</h3>

<p>With few exceptions, place code in a namespace. Namespaces
should have unique names based on the project name, and possibly
its path. Do not use <i>using-directives</i> (e.g.,
<code>using namespace foo</code>). Do not use
its path. Do not use <i>using-namespace</i>directives (e.g.,
<code>using namespace foo;</code>). Do not use
inline namespaces. For unnamed namespaces, see
<a href="#Internal_Linkage">Internal Linkage</a>.


</p><p class="definition"></p>
<h4>Using Declaration:</h4>
<p>Using declaration are allowed and can be used to refer to specific symbol from a namespace. For example</p>
<pre><code>Using ::foo::bar;</code></pre>

<h4>Additional Note With an Example:</h4>

<h5>Using NameSpace Directives: </h5>
<p>Using namespace directives brings the all the specified symbols/built-in-types from the specified NameSpace into the whatever current scope you are in, which leads to naming conflict and confusion(ambiguity). Therefore, they should be avoided.</p>

<p><strong>Example: </strong></p>
<pre><code>//Avoid This Practice:
using namespace std;
std::cout,std::endl or somethinglike std::string st = "Hello";</code></pre>

<h5>Using Declarations:</h5>
<p>Using Declarations allow you to bring namespace into current scope. This practice helps in avoiding the ambiguity(confusion) and which eventually keeps the code clear and manageable.</p>
<p><strong>Example to Use:</strong></p>
<pre><code>//Accepted
using namespace std;
cout,abs() or string str = "Hello,World";</code></pre>

<p>Namespaces subdivide the global scope
into distinct, named scopes, and so are useful for preventing
name collisions in the global scope.</p>
Expand Down Expand Up @@ -6020,4 +6041,4 @@ <h3 id="Windows_Code">Windows Code</h3>
</ul>
</div>
</body>
</html>
</html>