20 ms·
Last time we needed one we chose google. Not because we necessarily liked it but because then there was no argument about what the guide is or should be and so
by gumby 8y ago
Last time we needed one we chose google. Not because we necessarily liked it but because then there was no argument about what the guide is or should be and so we didn’t spend any time writing one.
It’s ok, not great, and definitely google specific (e.g. even google would prefer to use exceptions but for legacy reasons they can’t. So we couldn’t either)
- wutbrodo 8y agoWas there a reason you couldn't use GSG but change the section on exceptions? I don't think there are any logical dependencies between the exception ban and other parts of the style guide, but I could be mistaken. Every company I've worked at since starting at Google uses the GSG, so I've never had occasion to learn how to use exceptions in C++.
- gumby 8y agoYes there was a reason: once you change one thing you open everything else up for discussion as well. And while that would probably lead to a better guide (for us) than Google's, the time and thought involved in that would take away from solving the problems we wanted to solve in the first place.
- wutbrodo 8y agoHm yea, I figured that might be the case, but to me, the "this is only for legacy purposes" claim stands out enough from the rest of the GSG that I figured it would be easy to separate it from the rest of the guide. I obviously don't know the dynamics of your team though and totally find your explanation plausible.