News for hackers. Stuff that matters.
Re:C++ – From goto to std::transform by Ragnarork on Friday April 11, 2014 @05:23AM (#7571948)
What do you mean by "Lack of extra safety compared to C"? I'd have imagined the exact opposite, but maybe I'm missing something there.
Re:C++ – From goto to std::transform by pjmlp on Friday April 11, 2014 @07:49AM (#7572327)
C++ is way safer than C thanks to stronger type checking and what you can achieve via library types like STL collections.

However the C unsafety is still present due to the compatibility compromises with C in C++'s design.

With teams it is very hard to control what each developer makes use of, even with static analysis.

Re:C++ – From goto to std::transform by Ragnarork on Friday April 11, 2014 @08:48AM (#7572535)
That was kind of my point. I really think that if anything, C++ cannot be as unsafe as C. You can do crap in C++ just as well as you can do in C, but at least C++ gives you tools to do things way more safely IMO.
Re:C++ – From goto to std::transform by pjmlp on Friday April 11, 2014 @09:27AM (#7572685)
Yes, that is one reason why I never liked C, but do enjoy C++ for personal projects or when everyone on the team is quite comfortable with it.

For the other type of enterprise projects I rather use languages that follow Algol linage of memory safety.