November 14-16, Berlin, Germany
November 18-23, Wrocław, Poland
November 25, Wrocław, Poland
February 10-15, Hagenberg, Austria
March 19-21, Madrid, Spain
April 1-4, Bristol, UK
June 16-21, Sofia, Bulgaria
By Adrien Hamelin | Aug 4, 2017 01:22 PM | Tags: None
The end of the series.
Making things do stuff – Part 9
by Glennan Carnie
From the article:
As a final instalment in this series on hardware manipulation I thought I’d revisit read-only and write-only register types.
By Adrien Hamelin | Aug 4, 2017 01:20 PM | Tags: experimental community
Another report:
Trip Report: C++ Standards Meeting in Toronto, July 2017
by Botond Ballo
From the article:
A couple of weeks ago I attended a meeting of the ISO C++ Standards Committee (also known as WG21) in Toronto, Canada (which, incidentally, is where I’m based). This was the second committee meeting in 2017; you can find my reports on previous meetings here (November 2016, Issaquah) and here (February 2017, Kona). These reports, particularly the Kona one, provide useful context for this post.
By Adrien Hamelin | Aug 4, 2017 01:09 PM | Tags: performance c++14
Have you registered for CppCon 2017 in September? Don’t delay – Registration is open now.
While we wait for this year’s event, we’re featuring videos of some of the 100+ talks from CppCon 2016 for you to enjoy. Here is today’s feature:
Implementing `static` control flow in C++14
by Vittorio Romeo
Summary of the talk:
There has always been great interest in imperative compile-time control flow: as an example, consider all the existing `static_if` proposals and the recently accepted `constexpr_if` construct for C++17.
What if you were told that it is actually possible to implement imperative control flow in C++14?
In this tutorial, the implementation and design of a compile-time `static_if` branching construct and of a compile-time `static_for` iteration construct will be shown and analyzed. These constructs will then be compared to traditional solutions and upcoming C++17 features, examining advantages and drawbacks.
By Marco Arena | Aug 3, 2017 12:24 AM | Tags: community
I am very happy to announce we published all the videos of the Italian C++ Conference 2017:
C++ executors to enable heterogeneous computing in tomorrow's C++ today (Michael Wong)
Quicker Sorting (Dietmar Kühl)
Boost vs Qt: What Could They Learn From Each Other? (Jens Weller)
Monads for C++ (Bartosz Milewski)
Functional C++ for Fun and Profit (Phil Nash)
The second track is in Italian:
An overly simple C++ idiomatic pattern language for message-based product families (Carlo Pescio)
Lambda out: a simple pattern for generic output (Davide Di Gennaro)
Diversity and Inclusion in Microsoft (Paola Presutto)
Costruire un bridge C++ tra NodeJS e C# (Raffaele Rialdi)
Una libreria di rete asincrona scritta in C++ ispirata a Node.js (Stefano Cristiano)
The Italian C++ Conference 2017 videos are powered by Bloomberg.
By Adrien Hamelin | Aug 2, 2017 01:55 PM | Tags: c++17 basics
Another new feature.
C++17: Nested Namespaces
by Marc Gregoire
From the article:
The second post in this series of C++17 features highlights a tiny but very useful new feature called nested namespaces.
By Adrien Hamelin | Aug 2, 2017 01:52 PM | Tags: community
It is here!
CppCon 2017 Program Available
by Bryce Adelstein-Lelbach
From the article:
The program for CppCon 2017 is now live!
By Adrien Hamelin | Aug 2, 2017 01:48 PM | Tags: community
Have you registered for CppCon 2017 in September? Don’t delay – Registration is open now.
While we wait for this year’s event, we’re featuring videos of some of the 100+ talks from CppCon 2016 for you to enjoy. Here is today’s feature:
Examining applications that do not terminate on std::bad_alloc
by Sergey Zubkov
Summary of the talk:
System memory holds a special place in the hierarchy of program resources; its availability is the implied precondition for many innocuous lines of code, from std::string::substr() to passing std::function＜＞ by value. The ability to always create another object is ingrained in the OOP mindset so much that it is often said that immediate termination is the cleanest way to handle memory allocation failures in most situations. Nevertheless, C++, when consistently applying RAII, makes it possible to treat memory allocation exactly as any other resource acquisition.
To what degree do actual applications take advantage of that possibility and what responses to allocation failures are there in the wild? This presentation will examine over 300 open source projects that incorporate explicit handling for std::bad_alloc, examine the causes (it’s not always “out of memory”), response strategies (it’s more than just rollback), and related practical considerations.
By Felix Petriconi | Aug 1, 2017 11:33 PM | Tags: intermediate
In this article "No Bugs" Hare outlines the possibility to run C++ code in the major four web browsers.
(Not Really So) New Niche for C++: Browser!?
by "No Bugs" Hare
From the article:
For quite a long while, C++ had been losing popularity; for example, as reported in [Widman16], in 2016 it got 7% less of the listings on Dice.com compared with a year earlier; and according to [TIOBE17], from the C++ Golden Age in 2004 till 2017, the C++ share fell from ~17% to a measly 6%.
As all of us (as in, ‘hardcore C++ fans’) know , this has nothing to do with the deficiencies of C++; rather it is related to an observation that the time of downloadable clients (which was one of the main C++ strongholds) has changed into the time of browser-based clients – and all the attempts to get C++ onto browsers were sooo ugly (ActiveX, anyone?) that this didn’t really leave a chance to use C++ there.
Well, it seems that this tendency is already in the process of being reverted:
C++ can already run on all four major browsers – and moreover, it has several all-important advantages over JavaScript, too.
And this – not too surprisingly – is what this article is all about.
