aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/_posts
diff options
context:
space:
mode:
Diffstat (limited to '_posts')
-rw-r--r--_posts/2015-07-03-std-call-once-bug.md2
-rw-r--r--_posts/2017-01-07-building-boost.md2
-rw-r--r--_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md1
3 files changed, 5 insertions, 0 deletions
diff --git a/_posts/2015-07-03-std-call-once-bug.md b/_posts/2015-07-03-std-call-once-bug.md
index 5a263fc..98d3d26 100644
--- a/_posts/2015-07-03-std-call-once-bug.md
+++ b/_posts/2015-07-03-std-call-once-bug.md
@@ -5,6 +5,8 @@ excerpt: >
In this post I will describe a nasty bug I've stumbled upon in the C++
Standard Library implementation shipped with Microsoft Visual Studio
2012/2013.
+custom_css:
+ - syntax.css
---
I've recently come across a nasty standard library bug in the implementation
shipped with Microsoft Visual Studio 2012/2013.
diff --git a/_posts/2017-01-07-building-boost.md b/_posts/2017-01-07-building-boost.md
index 77b4d00..1a73908 100644
--- a/_posts/2017-01-07-building-boost.md
+++ b/_posts/2017-01-07-building-boost.md
@@ -4,6 +4,8 @@ layout: post
excerpt: >
This post describes the process of building Boost on Windows using either
Visual Studio or the combination of Cygwin + MinGW-w64.
+custom_css:
+ - syntax.css
---
Below you can find the steps required to build Boost libraries on Windows.
These steps tightly fit my typical workflow, which is to use Boost libraries in
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 e22ab21..24f9287 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
@@ -6,6 +6,7 @@ excerpt: >
for function definitions?
custom_css:
- snippets.css
+ - syntax.css
snippets_root_directory: snippets/static_vs_inline_vs_unnamed_namespaces/
snippets:
static: