aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorEgor Tensin <Egor.Tensin@gmail.com>2017-06-30 19:03:07 +0300
committerEgor Tensin <Egor.Tensin@gmail.com>2017-06-30 19:03:45 +0300
commit51914247d7203f20c68ada9c86031ada7eeba0a7 (patch)
treee844646781415f4a5d9adb7cdb215e5cf7a6d3b8
parentenable syntax highlighting (diff)
downloadjekyll-theme-51914247d7203f20c68ada9c86031ada7eeba0a7.tar.gz
jekyll-theme-51914247d7203f20c68ada9c86031ada7eeba0a7.zip
static-vs: namespace&nbsp;{
-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&nbsp;{
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.