3 ms·
> Well, back when I wrote C++ for a living I tried to keep up with better practices and newish, more compact and sensible language features. That's fine, but d
by locknitpicker 5mo ago
> Well, back when I wrote C++ for a living I tried to keep up with better practices and newish, more compact and sensible language features.
That's fine, but definitely something that does not happen in professional settings. You simply don't look at a codebase with a few million LoC and decide on a whim that you are going on to, say, replace all raw pointers with smart pointers. That is not going to happen. That definitely did not happen at all.
May I remind you that Google's C++ coding guidelines discourage exceptions because they do not have the resources to refactor all their code to be exception safe? Google doesn't have the man power but you do?
- zabzonk 5mo agoNot particularly relevant here, but may I point out that Google's C++ guidelines are generally seen as bad, and really only applicable to someone at Google scale, which you are almost certainly not.
- locknitpicker 5mo ago> Not particularly relevant here, but may I point out that Google's C++ guidelines are generally seen as bad (...) I don't have a dog in the race, but this is the first time I ever heard anyone express this opinion. Google's C++ guidelines are the first thing that critics cite when complaining about exceptions, and they do so as an example and not as something "bad". They also have nothing to do with scale, really. That's a puzzling statement. I have no idea what compels you to make that claim.