3 ms·
The guidelines seem like a document to me: https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md https://github.com/isocpp/CppCoreGuideli
by icebraining 9y ago
The guidelines seem like a document to me: https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md https://github.com/isocpp/CppCoreGuidelines/blob/master/CppC...
- dingo_bat 9y agoYou don't have to read them. The compiler will enforce them.
- icebraining 9y agoOh, ok, I didn't know that, thanks. Enforcing guidelines seems a bit like a contradiction in terms :)
- deleted 9y ago[deleted]
- Jweb_Guru 9y agoThe C++ compiler can't enforce many of these rules (and many of the ones it does claim to enforce, it only does heuristically), and the document itself is not shy about admitting that. It also makes quite clear that it expects not just mechanical checking, but things like peer review, to take these guidelines into account--meaning yes, you are expected to know a large portion of the document. Also, a lot of the listed enforcement mechanisms are literally just flagging suspicious code--you would have to disable a tremendous number of such flags to execute many perfectly reasonable programs. Stop misleading people about the contents of this document actually being enforced by the compiler, please.