Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 5
    An educated userbase or new constructs aren't really diminishing the rope though. They're just work-arounds so less people end up hung. Though this is all good commentary on Effective C++ and its context in the language's evolution. Commented Aug 26, 2012 at 0:47
  • 3
    No. It's about how a bunch of the items in Effective C++ are concepts that could equally apply to any value-typed object-orientated language. And educating the userbase to code actual C++ instead of C is definitely diminishing the rope that C++ gives you. Also, I would expect that new language constructs are diminishing the rope. It's about how just because the C++ Standard defines malloc does not mean that you should do it, any more than just because you can whore goto like a bitch means that it's rope you can hang yourself with. Commented Aug 26, 2012 at 9:42
  • 3
    Using the C parts of C++ is no different to writing all your code unsafe in C#, which is just as bad. I could list every pitfall of coding C# like C as well, if you'd like. Commented Aug 26, 2012 at 9:43
  • @DeadMG : so really the question should be "a C++ programmer has enough rope to hang himself as long as he is a C programmer" Commented Aug 26, 2012 at 14:08
  • "Plus, the proportion of the C++ population who are still sufficiently stupid, uninformed, or both to do things like manual memory management is a lot lower than before." Citation needed. Commented Aug 27, 2012 at 6:24