Difference between revisions of "C++11"

From Inkscape Wiki
Jump to navigation Jump to search
 
(12 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== C++11 usage status ==
+
== Usage status ==
The table lists C++11 features and whether they can be used in Inkscape or not (yet).
+
This table lists C++11 features and whether they can be used in Inkscape or not (yet).
 
Add C++11 features that you would like to use to the table, so that we know what to test for to increase the C++11 "allowance".
 
Add C++11 features that you would like to use to the table, so that we know what to test for to increase the C++11 "allowance".
 +
 +
See also [[C++17]]
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Feature
+
! Feature !! Can use? !! Comment
! Can use?
 
! Comment
 
 
|-
 
|-
| std::unique_ptr<>
+
| std::unique_ptr<> || style="background: lightgreen;" | from 0.93 || Replaces boost::scoped_ptr<> and std::auto_ptr<>
|not yet
 
| replaces boost::scoped_ptr<> and std::auto_ptr<>
 
 
|-
 
|-
| std::shared_ptr<>
+
| std::shared_ptr<> || style="background: lightgreen;" | from 0.93 || Replaces boost::shared_ptr<>
| not yet
 
|
 
 
|-
 
|-
| std::unordered_*<>
+
| std::unordered_*<> || style="background: lightgreen;" | from 0.93|| Replaces the hack in util/unordered-containers.h
|
 
| replaces the hack in util/unordered-containers.h
 
 
|-
 
|-
| auto (type inference)
+
| auto (type inference) || style="background: lightgreen;" | from 0.93 ||
| not yet
 
|  
 
 
|-
 
|-
| enum class
+
| enum class || not yet || Strong enum constants (take the name of the enum, can't be implicitly converted to <code>int</code>)
| not yet
 
|  
 
 
|-
 
|-
| range-based for
+
| range-based for || style="background: lightgreen;" | from 0.93 || Concise for loops with containers (Python alike)
| not yet
 
|  
 
 
|-
 
|-
| lambda functions
+
| lambda functions || not yet || In-place definitions for small functions
| not yet
 
| in-place defitions for small functions
 
 
|-
 
|-
| constructor delegation
+
| constructor delegation || not yet || Reduces boilerplate when an object has many constructors
| not yet
 
| reduces boilerplate when an object has many constructors
 
 
|-
 
|-
| right angle brackets in templates
+
| right angle brackets in templates || not yet || Fixes coding style oddity
| not yet
 
| fixes coding style oddity
 
 
|-
 
|-
| async, futures
+
| async, futures || not yet || Allows easy multithreading
| not yet
 
| allows easy multithreading
 
 
|-
 
|-
| toxic feature of doom
+
| std::initializer_list || not yet || Easier container initialization/assignation and implicit constructor calls
| style="background:Red;"| NO
 
| Never use this (in case we stumble upon C++11 features that we really don't like
 
 
|-
 
|-
| supported feature
+
| [https://en.cppreference.com/w/cpp/language/constexpr constexpr] || | ? || Additional meanings in C++14/C++17
| style="background:LightGreen;"| from 0.50
+
|-
|  
+
| toxic feature of doom || style="background: red;" | NO || Never use this (in case we stumble upon C++11 features that we really don't like)
 
|}
 
|}
  
== C++11 platform status ==
+
== Platform status ==
 +
 
 +
We need to keep coordinated with the section on [[Tracking_Dependencies#Distros|Distro Dependencies]].
 +
 
 +
Also see this page:
 +
* http://en.cppreference.com/w/cpp/compiler_support
  
Also see this page [http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport]
+
Note that <code>__cplusplus</code> is always <code>1</code> for GCC 4.6 that is used on Windows. So <code>#if __cplusplus < 201103L</code> or variants does not work to choose between C++03 or C++11 code.
  
Note that "__cplusplus" is always "1" for GCC 4.6 that is used on Windows. So "#if __cplusplus < 201103L" or variants does not work to choose between C++03 or C++11 code.
+
C++11 is well supported by all major compilers (MSVC has only partial support for constexpr). In fact C++14 and C++17 are also well supported by all platforms we support.
  
The table lists C++11 features and whether they work in trunk on a certain platform as advertised. If all lights are green -> set the light to green in the [C++11 usage status] section (taking current trunk version into account).
+
Compiler version when feature complete:
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Feature
+
!         !! GCC       !! Clang                                                                !! MSVC                                       
! Windows
 
! Mac
 
! Linux A
 
! Linux B
 
! Comment
 
|-
 
! Compiler
 
! TDM-GCC 4.6
 
!  
 
!  
 
!  
 
!  
 
|-
 
| unique_ptr<>
 
| style="background:LightGreen;"|
 
|
 
|
 
|
 
|
 
 
|-
 
|-
| shared_ptr<>
+
|C++11    || 4.8 (2014)|| 3.1 (2013) (3.3 for local thread storage and inheriting constructors) || 19 (except C99 preprocessor and constexpr) 
| style="background:LightGreen;"|  
 
|  
 
|
 
|  
 
|  
 
 
|-
 
|-
| auto
+
|C++14    || 5 (2015)  || 3.4 (2013)                                                            || 19 (2017) (19.1 for member initializers)
| style="background:LightGreen;"|
 
|
 
|  
 
|  
 
|  
 
 
|-
 
|-
| enum class
+
|C++17    || 7 (2017)  || 4  (2017) (5 for constexpr lambda expressions)                      || 19.14 (2017)
| style="background:LightGreen;"|
 
|
 
|  
 
|  
 
|  
 
 
|-
 
|-
| range-based for
+
|C++2a    || 10*      || 10*                                                                  || 19.22#
| style="background:LightGreen;"|
 
|
 
|  
 
|  
 
|  
 
 
|}
 
|}
 +
'*' Mostly complete
 +
'#' About half complete

Latest revision as of 09:11, 17 April 2020

Usage status

This table lists C++11 features and whether they can be used in Inkscape or not (yet). Add C++11 features that you would like to use to the table, so that we know what to test for to increase the C++11 "allowance".

See also C++17

Feature Can use? Comment
std::unique_ptr<> from 0.93 Replaces boost::scoped_ptr<> and std::auto_ptr<>
std::shared_ptr<> from 0.93 Replaces boost::shared_ptr<>
std::unordered_*<> from 0.93 Replaces the hack in util/unordered-containers.h
auto (type inference) from 0.93
enum class not yet Strong enum constants (take the name of the enum, can't be implicitly converted to int)
range-based for from 0.93 Concise for loops with containers (Python alike)
lambda functions not yet In-place definitions for small functions
constructor delegation not yet Reduces boilerplate when an object has many constructors
right angle brackets in templates not yet Fixes coding style oddity
async, futures not yet Allows easy multithreading
std::initializer_list not yet Easier container initialization/assignation and implicit constructor calls
constexpr ? Additional meanings in C++14/C++17
toxic feature of doom NO Never use this (in case we stumble upon C++11 features that we really don't like)

Platform status

We need to keep coordinated with the section on Distro Dependencies.

Also see this page:

Note that __cplusplus is always 1 for GCC 4.6 that is used on Windows. So #if __cplusplus < 201103L or variants does not work to choose between C++03 or C++11 code.

C++11 is well supported by all major compilers (MSVC has only partial support for constexpr). In fact C++14 and C++17 are also well supported by all platforms we support.

Compiler version when feature complete:

GCC Clang MSVC
C++11 4.8 (2014) 3.1 (2013) (3.3 for local thread storage and inheriting constructors) 19 (except C99 preprocessor and constexpr)
C++14 5 (2015) 3.4 (2013) 19 (2017) (19.1 for member initializers)
C++17 7 (2017) 4 (2017) (5 for constexpr lambda expressions) 19.14 (2017)
C++2a 10* 10* 19.22#

'*' Mostly complete '#' About half complete