Re:C++ the Good Parts (2014)
by pjmlp on Thursday October 01, 2020 @04:52AM
(#24648861)
So let me make it boom in C++,
Yes, I am making it fail on purpose, but copy-paste in enterprise codebases does wonders for code quality.
[ Parent
| on HN ]
You're reaching. I'm not sure it adds much to parent's point.
Using "new" is code smell. This is easily caught in code review.
Like those that Google does for Android?
Re:C++ the Good Parts (2014)
by CyberDildonics on Thursday October 01, 2020 @12:40PM
(#24653076)
Raw pointers for ownership are a bad idea, one of google's 30,000 programmers doing it doesn't change that. You are the only one pointing to google as an authority.
I am the only one, because the others don't care to point anything.
Re:C++ the Good Parts (2014)
by CyberDildonics on Friday October 02, 2020 @12:26PM
(#24664236)
Other people are pointing to the actual fundamental reasons these things exist and are valuable, you are pointing to a bizarre false authority as a desperate rationalization for not liking C++.
You are really harping on this one example.
I don't know what processes Google uses for the Android codebase, but in the main code base make_shared has only been available for a little while. Today, "new" is smell that should be caught in code review at Google. When was this committed?
Yes, because Google is a major contributor to ISO C++, LLVM, clang, has billions of C++ code, and yet fails to follow best practices.
So what to be expected by those companies that hardly have such a deep knowledge about C++ among their troops?