News for hackers. Stuff that matters.
Re:C++ the Good Parts (2014) by UncleMeat on Thursday October 01, 2020 @09:23AM (#24650523)
Using "new" is code smell. This is easily caught in code review.
Re:C++ the Good Parts (2014) by pjmlp on Thursday October 01, 2020 @10:59AM (#24651610)
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.
Re:C++ the Good Parts (2014) by pjmlp on Friday October 02, 2020 @10:49AM (#24663185)
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++.
Re:C++ the Good Parts (2014) by UncleMeat on Thursday October 01, 2020 @02:17PM (#24654323)
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?

Re:C++ the Good Parts (2014) by pjmlp on Friday October 02, 2020 @10:53AM (#24663242)
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?

Re:C++ the Good Parts (2014) by pkolaczk on Friday October 02, 2020 @02:38PM (#24665629)
Google is a huge company and the majority of its employees are not contributors to ISO C++.