aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/_posts
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md4
-rw-r--r--_posts/2018-02-18-peculiar-indentation.md4
2 files changed, 4 insertions, 4 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 6f9f3dc..94b5105 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
@@ -2,8 +2,8 @@
title: static vs. inline vs. namespace {
layout: post
excerpt: >
- Should I use <code>static</code>, <code>inline</code> or unnamed namespaces
- for function definitions?
+ Should I use `static`, `inline` or unnamed namespaces for function
+ definitions?
category: C++
custom_css:
- snippets.css
diff --git a/_posts/2018-02-18-peculiar-indentation.md b/_posts/2018-02-18-peculiar-indentation.md
index fceba33..6ec7c73 100644
--- a/_posts/2018-02-18-peculiar-indentation.md
+++ b/_posts/2018-02-18-peculiar-indentation.md
@@ -2,8 +2,8 @@
title: Peculiar Haskell indentation
layout: post
excerpt: >
- An explanation for nasty <code>parse error</code>s I used to get for nested
- <code>do</code> blocks.
+ An explanation for nasty `parse error`s I used to get for nested `do`
+ blocks.
category: Haskell
custom_css:
- syntax.css