From 3f86aa8f02ab3c13f636934f5fdb560d84339bce Mon Sep 17 00:00:00 2001 From: Egor Tensin Date: Sun, 18 Feb 2018 01:39:54 +0300 Subject: enable post categories --- _posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to '_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md') 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 static, inline 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. -- cgit v1.2.3