Standardization

N3982: Rvalue reference overloads for optional -- Andrzej KrzemieĊ„ski

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N3982

Date: 2014-04-03

Rvalue reference overloads for optional

by Andrzej Krzemieński

Excerpt:

... optional is just missing the rvalue reference overloads for these functions. This is what this proposal intends to fix: add rvalue reference overloads for member functions value and operator* (not for operator->, because it appears not to be implementable). I consider it a bug fix rather than a new feature, primarily because such an overload already exists and has been approved for function value_or. This is why I propose to fix it still in the first version of Fundamentals TS.

N3981: Removing trigraphs??! -- Richard Smith

[Ed: This one might get the pre-Rapperswil mailing award for funniest title... Thanks for the chuckle, Richard.]

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N3981

Date: 2014-05-06

Removing trigraphs??!

by Richard Smith

Excerpt:

Trigraphs continue to pose a burden on users of C++.

This paper proposes that trigraphs be removed entirely.

N3973: A Proposal to Add a Logical Const Wrapper -- Jonathan Coe and Robert Mill

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N3973

Date: 2014-05-12

A Proposal to Add a Logical Const Wrapper to the Standard Library Technical Report

by Jonathan Coe and Robert Mill

Excerpt:

We propose the introduction of a logical_const wrapper class that propagates const-ness to pointer-like (or reference-like) member variables.

N3972: Source-Code Information Capture -- Robert Douglas

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N3972

Date: 2014-05-17

Source-Code Information Capture

by Robert Douglas

Excerpt:

In Issaquah, I presented the idea of "Call-Site Informed Default Variables" to the reflection study group, to get a sense of what direction to pursue. The goal was to craft a feature to allow a function to capture information about the source code calling it, moving toward obsoleting function-macros for these use cases. The response from the room was largely positive, and requests were focused on the desire to present a means to convey source code information to be passed to a function. This proposal seeks to do just that.

N4010-12: Evolution Issues Lists -- Ville Voutilainen

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document numbers: N4010-12

Date: 2014-02-28

C++ Standard Evolution Active Issues List (Revision R07)

C++ Standard Evolution Completed Issues List (Revision R07)

C++ Standard Evolution Closed Issues List (Revision R07)

by Ville Voutilainen

Excerpt:

The purpose of this document is to record the status of issues which have come before the Evolution Working Group (EWG) of the INCITS PL22.16 and ISO WG21 C++ Standards Committee. Issues represent potential defects in the ISO/IEC IS 14882:2003(E) document, and proposed extensions to it.

C++ Status

A follow up on my proposal series & C++14 post:

C++ Status

by Jens Weller

From the Article:

This is the followup I promised after my last series for Issaquah. The current status of the standardization is that C++14 is on its final way to become a new ISO Standard, as you can see on the C++ Status Page of isocpp.org.

C++11/14 Standard & Standardization--Peter Sommerlad

Peter Sommerlad on C++11 and C++14 Standard(s) and Standardization:

Peter Sommerlad on C++11 and C++14 Standard(s) and Standardization

Created by Peter Sommerlad March 6, 2014

From the presentation:

Why is C++ in again?

• more computing per Watt!
  • mobile - battery powered
  • servers - cloud computing
  • high-performance computing & GPUs
• better abstractions than C
  • without performance price (e.g. of a VM)
  • embedded (higher-level type safety)
  • security (buffer overruns, pointers)

Slides (PDF)

Compiler support for C++11 and C++14

C++11 support is still an interesting topic, even that GCC and Clang now fully support it. Also the upcoming C++14 standard is already getting implemented by a lot of compilers. There are two very interesting publications about this topic in recent weeks, first, on italiancpp.org there is a PDF on C++11 and C++14 feature support for Visual C++, Intel, Clang and GCC. Also Just a few days ago, a interesting blogpost about this topic was published on C++Rocks, focussing on compiler and library support:

C++11/14 compiler and library shootout

by C++ Rocks

From the Article:

It’s been almost a year since my last comparison of C++11 support across different compilers, so I decided to take a break from working on my book about C++11/14 features in VS2013, and see how things have changed.