Commit 22abacb8 authored by Martin Dørum's avatar Martin Dørum

Fixed factual issue related to Clang

parent 8a2ef7ad
......@@ -80,12 +80,15 @@ Wrong. It turns out that in their quest to support code written for GCC, Clang
also defines the `__GNUC__`, `__GNUC_MINOR__`, and `__GNUC_PATCHLEVEL__`
macros, specifically to fool code which checks for GCC into thinking Clang is
However, it doesn't really go far enough;
<del>However, it doesn't really go far enough;
it defines the `__GNUC_*` variables to correspond to the the version of _clang_,
not the version of GCC which Clang claims to imitate.
Clang gained support for C11 in 3.6, but using our code,
we would conclude that it doesn't support C11 because `__GNUC__`
is 3 and `__GNUC_MINOR__` is 6.
is 3 and `__GNUC_MINOR__` is 6.</del>
Update: it turns out that Clang always pretends to be GCC 4.2, but the same
issue still applies; `__GNUC__` is 4, and `__GNUC_MINOR__` is 2, so it fails
our version check.
We can solve this by adding a special case for when `__clang__` is defined:
``` C
......@@ -73,6 +73,12 @@ html.home .posts .post .read-more {
border-radius: 5px;
/* content with display: inline-block doesn't get strikethrough in <del> */
.post .content del > code,
.post .content del *:not(pre) > code {
display: inline;
.post .content h2 {
border-bottom: 2px solid #222;
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment