Difference between revisions of "C++11"
Jump to navigation
Jump to search
(Auto, range-based for and unordered containers are all working) |
(<memory> should be safe now) |
||
Line 7: | Line 7: | ||
! Feature !! Can use? !! Comment | ! Feature !! Can use? !! Comment | ||
|- | |- | ||
| std::unique_ptr<> || | | std::unique_ptr<> || style="background: lightgreen;" | from 0.93 || Replaces boost::scoped_ptr<> and std::auto_ptr<> | ||
|- | |- | ||
| std::shared_ptr<> || | | std::shared_ptr<> || style="background: lightgreen;" | from 0.93 || Replaces boost::shared_ptr<> | ||
|- | |- | ||
| std::unordered_*<> || style="background: lightgreen;" | from 0.93|| Replaces the hack in util/unordered-containers.h | | std::unordered_*<> || style="background: lightgreen;" | from 0.93|| Replaces the hack in util/unordered-containers.h |
Revision as of 20:02, 16 August 2016
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".
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 |
toxic feature of doom | NO | Never use this (in case we stumble upon C++11 features that we really don't like) |
supported feature | from 0.93 |
Platform status
We need to keep coordinated with the section on Distro Dependencies.
Also see these pages:
- http://wiki.apache.org/stdcxx/C++0xCompilerSupport
- http://en.cppreference.com/w/cpp/compiler_support
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.
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 Usage status section (taking current trunk version into account).
Feature | Windows | Mac 10.6 | Mac 10.7 | Fedora 20 | Red Hat 7.0 | Red Hat 6.5 | Comment |
---|---|---|---|---|---|---|---|
TDM-GCC 4.6/4.9 (x64) | GCC 4.2 | Clang 3(?) | GCC 4.8.2 | GCC 4.8.2 | GCC 4.4.7 | ||
unique_ptr<> | Defined in <memory> | ||||||
shared_ptr<> | Defined in <memory> | ||||||
auto | |||||||
enum class | |||||||
range-based for |