March 11-13, Online
March 16-18, Madrid, Spain
March 23-28, Croydon, London, UK
March 30, Kortrijk, Belgium
May 4-8, Aspen, CO, USA
May 4-8, Toronto, Canada
June 8 to 13, Brno, Czechia
June 17-20, Folkestone, UK
September 12-18, Aurora, CO, USA
November 6-8, Berlin, Germany
November 16-21, Búzios, Rio De Janeiro, Brazil
By Blog Staff | Sep 24, 2013 07:31 AM | Tags: None
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: N3771
Date: 2013-09-22
Canadian C++14 Comments
by Hubert Tong, Michael Wong
By Meeting C++ | Sep 24, 2013 04:51 AM | Tags: standardization library intermediate c++14
This is the third part of my series about the C++ papers for Chicago:
C++ Papers for Chicago: Part 3 - Library
by Jens Weller
From the article:
This week the C++ committee meeting has started in Chicago, and we will hopefully see at its end, what improvements C++14 brings to C++11. And in this 3rd part of my series for the Chicago papers, I will start looking at the library proposals...
By Meeting C++ | Sep 20, 2013 10:24 AM | Tags: intermediate efficiency
A good article on extending streams correctly:
Don't couple streams with devices
by Marco Arena
From the article:
A couple of weeks ago, a friend of mine coded an output stream that outputted strings through Win32
OutputDebugStringfunction...
By Blog Staff | Sep 20, 2013 10:15 AM | Tags: None
Yesterday on SO:
A positive lambda: +[]{} -- What sorcery is this?
Does anyone know why this
#include <functional> int main() { auto test = +[]{}; // note the unary operator + before the lambda test = []{}; }works? It compiles fine with both GCC 4.7+ and Clang 3.2+. Is the code standard conforming?
By Blog Staff | Sep 19, 2013 08:20 AM | Tags: None
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: N3774
Date: 2013-09-19
C++ Needs Language Support For Vectorization
by Axel Naumann, Sandro Wenzel
Excerpt:
In this paper we argue that vectorization is a very different concept to parallelization and needs to be supported explicitly by the language. The lack of C++ support for explicit vectorization costs factors (2 to 4 in real code) of performance on current commodity hardware. We demonstrate why we believe vectorization is a much needed language feature. The arguments presented in this paper are based on, and accompanied by, performance measurements of code used at CERN.
By Blog Staff | Sep 19, 2013 03:59 AM | Tags: None
Now available:
POCO Stable Release 1.4.6p2 and Development Release 1.5.2 Available
From the announcement:
Stable release 1.4.6p2 contains mostly bugfixes, upgrades to some bundled libraries (expat, zlib and sqlite) and a few new features (e.g. ColorConsoleChannel). ...
Development release 1.5.2 adds the MongoDB client library, contains significant updates to the JSON library, adds all changes from 1.4.6p2 and a whole lot of other improvements and fixes. ...
By hendrixjl | Sep 18, 2013 09:50 AM | Tags: None
Fro
m Cloudius comes OSv: An alternative to Linux running in a virtual machine, written in modern C++. Cloudius is a startup formed by a group of ex-Red Hat OS virtualization experts.
Announcement: OSv, a new open-source operating system for virtual machines
InformationWeek, Charles Babcock: "Cloudius Takes On Linux as Cloud OS"
From the announcement:
Another refreshing feature of OSv is that is written in C++. It's been 40 years since Unix was (re)written in C, and the time has come for something better.
C++ is not about writing super-complex type hierarchies (as some people might have you believe). Rather, it allowed us to write shorter code with less boiler-plate repetition and less chances for bugs. It allowed us to more easily reuse quality code and data structures. And using newly standardized C++11 features, we were able to write safe concurrent code with standard language features instead of processor-specific hacks. And all of this with zero performance overheads -- most of C++'s features, most notably templates, are compile-time features which result in no run-time overhead compared to C code.
By Blog Staff | Sep 16, 2013 09:17 PM | Tags: None
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: N3767
Date: 2013-09-13
WG21 Teleconference 2013-09-13 Minutes
by Kyle Kloepper
This was the pre-Chicago WG21 administrative telecon.
By Blog Staff | Sep 16, 2013 09:08 PM | Tags: None
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: N3773
Date: 2013-09-12
async and ~future (Revision 4)
by Herb Sutter, Chandler Carruth, Niklas Gustafsson
Excerpt:
N3637 documented the consensus of SG1 in Bristol. This paper is a minor update to N3637 to make the “change std::async” part of the proposal explicitly separable by updating the example code and adding three alternate sections to section 3 (3.1, 3.2, 3.3). This is to reflect that the main question at the end of Bristol was about how changing std::async affects binary compatibility, and to reflect the “N3637 except {remove|deprecate|leave-as-is} std::async instead of changing it” straw polls that had the most support in the July Santa Clara SG1 meeting.
By Meeting C++ | Sep 16, 2013 09:08 AM | Tags: intermediate experimental c++14 advanced
The second part of my series about the papers for Chicago:
Papers for Chicago: Core, Concepts and Evolution
by Jens Weller
From the article:
This time I cover core, concepts, evolution and filesystem. I decided to keep the format with grouping the papers by domain, it makes it easier to have an overview.