3 ms·
you have to write those rules down in meticulous detail,... and at that point you're asking your contributors to study and internalize a large and complicated l
by stcredzero 15y ago
you have to write those rules down in meticulous detail,... and at that point you're asking your contributors to study and internalize a large and complicated list of what is and isn't allowed
What about a short list of what is allowed, with a strict whitelisting policy? I recall from years ago a version of the Taligent C++ conventions that was fairly compact. (Which was also the subject of Bjarne Stroustrup's quip about trying to use C++ as "a poor man's Smalltalk.")
Automated tools that embody the blacklists might be useful here as well, provided that they can be scripted quickly. I'm not sure if there are parser-based tools for C++ that would fit the bill. The article's problems with non-empty constructors seem amenable to automated blacklisting. Unfortunately, even with such tools, this strategy entails lots of work up-front by project organizers.
- BMarkmann 15y agoTo save someone else the trouble of googling: http://pcroot.cern.ch/TaligentDocs/TaligentOnline/DocumentRoot/1.0/Docs/books/WM/WM_54.html http://pcroot.cern.ch/TaligentDocs/TaligentOnline/DocumentRo...
- stcredzero 15y agoThese aren't the conventions you are looking for. (The ones I remember call for all member functions to be virtual.)