ACCU 2017 Schedule has been published—ACCU conference committee

The schedule for the upcoming ACCU 2017 conference in Bristol, UK from 2017-04-26 to 2017-04-29 has been published.

ACCU 2017 Schedule

by ACCU conference committee

About the schedule

Again we have very strong C++ tracks this year!

Beside a closing keynote by Herb Sutter, where he wants to make a public announcement on an upcoming C++ development, there will be great C++ talks by members of the ISO C++ committee, other known C++ speakers and new faces to the C++ world.

Four full day tutorials take place the day before the conference, three with C++ content.

So don't forget to register

C++ User Group Meetings in January

The January listing of upcoming User Group meetings!

C++ User Group Meetings in January

by Jens Weller

From the article:

The new year has begun, and as I just returned the listing of the User Group Meetings is a bit late...

Yet still, 37 Meetings in January are listed, 7 of them in Austin, as there is a study group for Modern C++ now.

There are 3 new C++ User Groups: Nashua, NH, Vienna (Qt), Austin (Mentoring & Study Group).

C++Now 2017 Call for Submissions is Live

C++Now 2017 will be held in Aspen, May 15–20, 2017.

C++Now 2017 Call for Submissions

From the invitation:

C++Now builds upon the resounding success of previous BoostCon and C++Now conferences, We look forward to considering your proposals, among those from leading speakers from the entire C++ community, to make C++Now 2017 even better.

The C++Now Conference is dedicated to discussion and education about C++, an open and free language and standard.  Our Conference will focus on discussion and education about open source software usage and developments in the C++ developer and user community. To reflect the breadth of the C++ and Boost communities, the conference includes sessions aimed at three constituencies: C++ and Boost end-users, hard-core library and tool developers, and researchers pushing the boundaries of computing. The program fosters interaction and engagement within and across those groups, with an emphasis on discussion.

As a multi-paradigm language, C++ is a melting pot with the most compelling ideas from other programming communities blended in powerful ways. Historically, some of the most popular sessions at C++Now have highlighted these concepts, from DSLs to functional programming to transactional memory and more.  Bring your C#, Python, Ruby or Haskell influences to bear in an environment that will broaden their exposure.

Presentations at C++Now 2017 should generally focus on the now established C++11 and C++14 standards, the upcoming C++17 standard, and how those standards shape C++’s future. However, by no means is this intended to restrict the topics of proposals we hope to see. Any other topic related to C++, as described below, is suitable for submission.

This year’s window for submitting is shorter than normal. Submissions must be in by February 3rd, less than four weeks away.

A new way of blogging about C++—Yehonathan Sharvit

A very interesting plugin for our blogs:

A new way of blogging about C++

by Yehonathan Sharvit

From the article:

This blog post is about to show a new way of blogging about C++.

Look at a typical blog post about C++: The post usually presents a couple of code snippets. As I see it, there are two pains with code snippets:

  1. they contain the input and the output but not the actual evaluation of the input
  2. it’s impossible for the reader to modify the output...

My take on variant—Jonathan Müller

An interesting point of view and implementation of a variant in one article!

My take on variant

by Jonathan Müller

From the article:

C++17 is going to add std::variant. To quote the linked documentation, it is a “type-safe union”. A union is like a struct, but can only store one member at a time. This has many applications, but sadly it doesn’t mix well with non-trivial types, you have to call the destructor yourself etc. Furthermore, nothing prevents you from accessing a union member that isn’t active.

std::variant fixes that. It correctly calls the destructor when switching the active member, it prevents invalid access, etc. However, I’m not quite happy with it and I needed an implementation now. So I’ve decided to implement my own variant as part of my type_safe library.

It was a fun challenge and since my previous attempt was two years ago, I could improve it a lot. Let’s go through some of my design decisions.

Report from using std::cpp 2016—Daniel Garcia

Daniel Garcia reports from the recent std::cpp conference:

Conference Report

by Daniel Garcia

From the report:

Last November 24th we had the fourth edition of using std::cpp, our annual spanish conference on C++ for professional developers. The conference is a one-day free event held every year at University Carlos III of Madrid, in Leganés. We had around 200 registered attendees (most of them professional developers).

We would like to share some answers from the evaluation questionaries:

  • 75% of attendees were professional developers, 14% were students, and 11% were academics.
  • 92% declared they use regularly C++.
  • The most popular version of C++ was C++11 (73%), followed by C++98/03 (63%) and C++14 (21%). Note that you could vote for more than one. However, no one declared to make use of any extension or TS.
  • Most popular compiler was gcc (60%), followed by Microsoft (57%), and clang++ (14%).
  • When we asked for domains a found a split among multiple sectors: telco (20%), aerospace/naval (11%), civil engineering (9%), bank/finance/insurance (7%), developer tools (7%), videogames (6%), research/academia (4%), transport (4%), industrial manufacturing (2%).


Return early and clearly—Arne Mertz

How to return well:

Return early and clearly

by Arne Mertz

From the article:

There are different guidelines out there about where and how many return statements to use in a function, e.g. return only once at the end of the function or return early and often. Which one makes for the most readable code?