There’s an example at the end of this lesson which you can use to test if you set up your compiler to use C++17 correctly. This should not impact your overall experience too heavily (especially in the early lessons).Ĭ++14 is the minimum language standard for a decent experience on this site. If this is not possible for some reason, you will need to skip some content, and alter some examples so that they will compile. If your compiler doesn’t support C++17, we recommend upgrading to one that does.

Using the C++17 language standard will also provide a good experience. To take full advantage of all the lesson content, we recommend using the C++20 language standard if your compiler supports it. Some C++20 content is available for those with C++20 compatible compilers.

This website currently targets the C++17 standard, meaning our lessons and examples assume your compiler is C++17 capable. You may still see the code names used in places (especially for upcoming version of the language standard, which won’t have a final name yet). For example, C++11 was called c++1x while it was being worked on.

Consequently, in-progress language standards are given code names, which are then replaced by the actual names upon finalization of the standard. However, when a new language standard is being agreed upon, it’s not clear in what year the finalization will take place. If you wish to use a different language standard (and you probably will), you’ll have to configure your IDE/compiler to do so.Ĭode names for in-progress language standardsįinalized language standards are named after the years in which they are finalized (e.g. With many different versions of C++ available (C++98, C++03, C++11, C++14, C++17, C++20, etc…) how does your compiler know which one to use? Generally, a compiler will pick a standard to default to (typically not the most recent language standard).

Codeblocks compiler not c++11