Skip to main content

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
  • 4
    Questions asking for long lits of things are not well suited for this site. But you can lookup the breaking changes at the official standards, as Caleth pointed out. Unfortunately, asking for 3rd party resources is off-topic for the site. If you ask me for a change similar to the change from Python2 to Python3, I think Stroustrup intentionally chose to make C++ not 100% backwards compatible to C, for the purpose of creating a more powerful language. Commented Jan 20, 2023 at 10:00
  • 1
    Closed now, but the C++ breakages have tended to be in obscure corners and not to affect most codebases, while the print change affected almost every single script, and (more importantly) the unicode change broke almost every single piece of text handling. Also, you can often use older C++ libraries in updated programs, while the same was not true of python and crippled the upgrade. Commented Jan 20, 2023 at 13:57
  • 2
    There was a certain amount of breakage before standardisation, but that was way back in the 90s. It's like asking about pre-ANSI C. Commented Jan 20, 2023 at 14:00
  • The answer will be different for C and C++, please pick one and focus on one. Commented Aug 16 at 20:52
  • 2
    Quite common is new features using new keywords that cannot be used as plain identifiers anymore. For example, at some point “int restrict = 0;” became invalid C. Commented Aug 17 at 4:29