March 23-28, London, UK
By Adrien Hamelin | Oct 8, 2015 12:51 PM | Tags: c++11 basics
Bitesize Modern C++ :
std::arrayby Glennan Carnie
From the article:
C++98 inherited C’s only built-in container, the array. Arrays of non-class types behave in exactly the same way as they do in C. For class types, when an array is constructed the default constructor is called on each element in the array...
By Adrien Hamelin | Oct 5, 2015 09:31 AM | Tags: c++11 advanced
An interesting article about some dangerous allocators:
AllocatorAwareContainer: Introduction and pitfalls of propagate_on_container_XXX defaults
by Jonathan Müller
From the article:
While I was writing the std_allocator adapter of foonathan/memory I've learned some not so well-known facts about the STL
AllocatorandAllocatorAwareContainerconcepts I'd like to share. Let's take a deep breath and dive in into an aspect of the STL containers that isn't that well covered: Allocator storage.I will explain the comparison properties of Allocators, show the C++11
propagate_on_container_XXXtraits and how the combination of the two can lead to an unnecessary pessimization and a probably not widely known case of undefined behavior...
By Adrien Hamelin | Oct 5, 2015 08:00 AM | Tags: community
Trip report from Meeting C++:
I attended CppCon, and all I got...
by Jens Weller
From the article:
... was an awesome conference! So this is my trip report. I really enjoyed the week in Bellevue, it was a pleasure to see so many of you again, so I want to thank Jon Kalb for organizing a great CppCon for the 2nd time...
By Mantosh Kumar | Oct 4, 2015 08:25 AM | Tags: None
More presentation materials from CppCon 2015 is now available on GitHub. You will be able to find them at github.com/cppcon/cppcon2015. Enjoy!
By Meeting C++ | Oct 2, 2015 06:54 AM | Tags: user groups community
The monthly overview on upcoming user group meetings:
C++ User Group Meetings in October
by Jens Weller
From the article:
5.10 C++ UG Dublin - C/C++ Meeting with 3 Talks
7.10 C++ UG Saint Louis - Intro to Unity\, Scott Meyers "gotchas"\, Group exercise
7.10 C++ UG Washington, DC - Q & A / Info Sharing
13.10 C++ UG New York - Joint October C++ Meetup with Empire Hacking
14.10 C++ UG Utah - Regular Monthly Meeting
14.10 C++ UG San Francisco/ Bay area - Presentation and Q&A
19.10 C++ UG Austin - North Austin Monthly C/C++ Pub Social
20.10 C++ UG Berlin - Thomas Schaub - Introduction to SIMD
20.10 C++ UG Hamburg - JavaX (really?)
21.10 C++ UG Washington, DC - Q & A / Info Sharing
21.10 C++ UG Bristol - Edward Nutting
21.10 C++ UG Düsseldorf - CppCon trip report & Multimethods
21.10 C++ UG Arhus - Lego & C++
24.10 C++ UG Italy - Clang, Xamarin, MS Bridge, Google V8
28.10 C++ UG San Francisco/ Bay area - Workshop and Discussion Group
29.10 C++ UG Bremen - C++ User Group
By Meeting C++ | Oct 2, 2015 03:41 AM | Tags: None
An alternative listing of the papers sorted by mailing & subgroups:
This years C++ Committee papers sorted by mailing and subgroup
by Jens Weller
From the article:
I used to do overviews on all papers for a meeting, and when I find the time, I will do this for upcoming meetings again. I will try to post a best-of later, with all the good stuff on concepts, modules and more later. Currently I'm to busy, I just got back from CppCon, and will go to the Qt World Summit next week (meet me there!).
So, in the mean time you can take take a look for yourself, as what follows is the list off all papers submitted this year, sorted by mailings and then subgroups. My awesome paper crawler tool did finally its job correct...
By Adrien Hamelin | Sep 28, 2015 08:33 AM | Tags: community c++14 basics
The Problem, The Culprits, The Hope
by Tony “Bulldozer00” (BD00) DaSilva
From the article:
Bjarne Stroustrup’s keynote speech at CppCon 2015 was all about writing good C++11/14 code. Although “modern” C++ compilers have been in wide circulation for four years, Bjarne still sees:
I’m not an elite, C++ committee-worthy, programmer, but I can relate to Bjarne’s frustration...
By Adrien Hamelin | Sep 24, 2015 02:36 PM | Tags: basics
Everything is in the title:
Core C++ - Destructors and RAII
by Anthony Williams
From the article:
Though I love many features of C++, the feature that I think is probably the most important for writing robust code is deterministic destruction and destructors...
By Adrien Hamelin | Sep 24, 2015 02:29 PM | Tags: c++11 basics
noexcept?
Bitesize Modern C++ : noexcept
by Glennan Carnie
From the article:
We have some basic problems when trying to define error management in C:
- There is no “standard” way of reporting errors. Each company / project / programmer has a different approach
- Given the basic approaches, you cannot guarantee the error will be acted upon.
- There are difficulties with error propagation; particularly with nested calls.
The C++ exception mechanism gives us a facility to deal with run-time errors or fault conditions that make further execution of a program meaningless...
By Felix Petriconi | Sep 21, 2015 04:55 AM | Tags: c++14 c++11
Bjarne Stroustrup and Herb Sutter are currently editing the newly created C++ Core Guidelines on GitHub.
C++ Core Guidelines
From the abstract section of the page:
This document is a set of guidelines for using C++ well. The aim of this document is to help people to use modern C++ effectively. By "modern C++" we mean C++11 and C++14 (and soon C++17). In other words, what would you like your code to look like in 5 years' time, given that you can start now? In 10 years' time?
The guidelines are focused on relatively higher-level issues, such as interfaces, resource management, memory management, and concurrency. Such rules affect application architecture and library design. Following the rules will lead to code that is statically type safe, has no resource leaks, and catches many more programming logic errors than is common in code today. And it will run fast - you can afford to do things right.
We are less concerned with low-level issues, such as naming conventions and indentation style. However, no topic that can help a programmer is out of bounds.
Our initial set of rules emphasize safety (of various forms) and simplicity. They may very well be too strict. We expect to have to introduce more exceptions to better accommodate real-world needs. We also need more rules.
You will find some of the rules contrary to your expectations or even contrary to your experience. If we haven't suggested you change your coding style in any way, we have failed! Please try to verify or disprove rules! In particular, we'd really like to have some of our rules backed up with measurements or better examples.
You will find some of the rules obvious or even trivial. Please remember that one purpose of a guideline is to help someone who is less experienced or coming from a different background or language to get up to speed.
The rules are designed to be supported by an analysis tool. Violations of rules will be flagged with references (or links) to the relevant rule. We do not expect you to memorize all the rules before trying to write code.
The rules are meant for gradual introduction into a code base. We plan to build tools for that and hope others will too.
Comments and suggestions for improvements are most welcome. We plan to modify and extend this document as our understanding improves and the language and the set of available libraries improve.
