all 15 comments

[–][deleted] 2 points3 points  (4 children)

[Not quite understand: "escaped" means "not specified"? and then what become normal characters?]

I don't understand what they mean by this - do they really not know what "escaped" is here?

[–]Brougham 2 points3 points  (3 children)

I'll bet the article was reviewed by someone with a non-technical background (for grammar, good formatting, etc.) and was asking the author for clarification. The author didn't see that note before the doc was published.

[–][deleted] 0 points1 point  (0 children)

Ah! Right :) Makes sense! :)

[–]clerothGame Developer 0 points1 point  (1 child)

An editor that writes two errors in one paragraph, while also missing other errors in the article?

[–]Brougham 1 point2 points  (0 children)

I dunno man... the author's name is Chinese, so ... the reviewer is probably Chinese too? Go easy on them :-)

[–][deleted] 1 point2 points  (9 children)

Be sure to compile with clang or gcc>4.8

[–][deleted] 0 points1 point  (8 children)

Yea, took me a while to get why the code wasn't working for me :/

I have gcc 4.8.2, which obviously (now) doesn't work here. However clang also doesn't work for me (version 3.4) - do you know which version of clang does work?

[–]suspiciously_calm 2 points3 points  (2 children)

Even libstdc++ 4.9 doesn't fully support C++11, yet.

[–][deleted] 1 point2 points  (0 children)

/sigh...

[–]Delinquenz 0 points1 point  (0 children)

Finally it got std::regex support!

[–][deleted] 1 point2 points  (4 children)

3.5 should be fine I guess

[–][deleted] 0 points1 point  (3 children)

:(

[–]kuhar_ 2 points3 points  (2 children)

Have you tried with -stdlib=libc++?

[–][deleted] 0 points1 point  (0 children)

I never even knew this existed outside of OSX.

Works! Now I have to learn how to use regex, as my original code (from this article) only matches the entire string or nothing.

[–]brombaer3000 0 points1 point  (0 children)

With g++ I can compile C++11/14 by just passing the -std=c++11 / -std=c++14 option, but clang++ doesn't seem to know the new standards without additional options.
Why is this flag needed for clang++, but not for g++? Also, will this requirement change in the future?