Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The point is that the practices that almost unavoidably lead to bugs in C code are not even tempting in modern C++. So, if you are interested in correctness and memory safety, stepping to modern C++ provides more value for time invested than the sum of most other choices.

Equating the two is extremely common, even by people who are certainly equipped to know better. When you feel a need to tar C++ as if it were C, you signal the weakness of your argument before you have even expressed it.



"Modern C++" is a term that mostly just means "C++ sans the C parts". So yeah, it's different than C.


> you signal the weakness of your argument before you have even expressed it.

Please turn down your flamethrower, that style of conversation is not welcome here.


Writing "C/C++", in contexts where it is implied they have the same failure modes, is provocative. Don't like response, don't provoke.

It is fine when talking about ABI or object-code generation.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: