aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
diff options
context:
space:
mode:
Diffstat (limited to '_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md')
-rw-r--r--_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md b/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
index 8094c3d..6f9f3dc 100644
--- a/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
+++ b/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
@@ -4,6 +4,7 @@ layout: post
excerpt: >
Should I use <code>static</code>, <code>inline</code> or unnamed namespaces
for function definitions?
+category: C++
custom_css:
- snippets.css
- syntax.css
@@ -154,7 +155,7 @@ name, but are defined in different translation units.
{: .alert .alert-info }
`namespace {`
-------------------
+-------------
With respect to function definitions, unnamed namespaces are, according to my
understanding, quite similar to the `static` keyword.