aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/_posts/2015-07-03-std-call-once-bug.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--_posts/2015-07-03-std-call-once-bug.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/_posts/2015-07-03-std-call-once-bug.md b/_posts/2015-07-03-std-call-once-bug.md
index 0fd6c30..4b99bfd 100644
--- a/_posts/2015-07-03-std-call-once-bug.md
+++ b/_posts/2015-07-03-std-call-once-bug.md
@@ -1,5 +1,5 @@
---
-title: std::call_once bug in Visual Studio 2012/2013
+title: std::call_once bug in Visual C++ 2012/2013
layout: post
excerpt: >
In this post I will describe a nasty bug I've stumbled upon in the C++
@@ -252,7 +252,7 @@ simple example above to misbehave.
The [complete code sample] to demonstrate the misbehaviour described above can
be found in this blog's repository.
-[complete code sample]: {{ site.github.repository_url }}/tree/gh-pages/src/posts/std_call_once_bug_in_visual_studio_2012_2013
+[complete code sample]: {{ site.github.repository_url }}/tree/gh-pages/src/posts/std_call_once_bug
Resolution
----------