My head's been mostly in Java and Python the last three years, and my old work's C++ practices were woefully out-of-date. I really appreciate the work put into the CppCoreGuideline documents ... it's real complex, though.

I was dreading getting back to C++ with the Rule-of-3 and now the Rule-of-5 -- what a pain! Fortunately I ran into the Rule-of-Zero as described here: http://accu.org/index.php/journals/1896. The CppCoreGuidelines have a more restrictive Rule-of-Zero but allude to the link's form . . . the only way I'll get back to C++ is if I can avoid move-constructor and move-assignment for the majority of my work ... and the link provides the answer!

> The rules are designed to be supported by an analysis tool. Violations of rules will be flagged with references (or links) to the relevant rule. We do not expect you to memorize all the rules before trying to write code.

But I agree, a short guide for C++ with the most important stuff in it would be nice.

It will be great if there is a similar guidance for C, i.e. CCoreGuidelines.