aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
-rw-r--r--_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md4
1 files changed, 2 insertions, 2 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 24f9287..69bd4f9 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
@@ -1,5 +1,5 @@
---
-title: static vs. inline vs. namespace {
+title: static vs. inline vs. namespace {
layout: post
excerpt: >
Should I use <code>static</code>, <code>inline</code> or unnamed namespaces
@@ -154,7 +154,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.