CppCon: Announcing 2016 Dates
It has been announced: it will be on the week of September the 18th:
CppCon: Announcing 2016 Dates
C++ User Group Meetings in November
The montly overview on upcoming C++ User Group Meetings:
23 C++ User Group meetings in November
by Jens Weller
The list:
4.11 C++ UG Saint Louis - Unit Test++, Scott Meyers "gotchas", group exercise
4.11 C++ UG Washington, DC - Q & A / Info Sharing
4.11 C++ UG Austin - OpenMP
9.11 C++ UG Edinburgh - C++ Edinburgh
9.11 C++ UG Zentralschweiz - Coding Dojo
11.11 C++ UG Utah - Regular Monthly Meeting
11.11 C++ UG San Francisco/ Bay area - Presentation and Q&A
12.11 C++ UG NRW/Aachen - Variadic Templates und TMP ohne Rekursion
12.11 C++ UG Dresden - User perspektive on Catch
16.11 C++ UG Austin - North Austin Monthly C/C++ Pub Social
17.11 C++ UG Berlin - November Meetup
17.11 C++ UG Hamburg - OpenCL
18.11 C++ UG San Francisco/ Bay area - Workshop and Discussion Group
18.11 C++ UG Warsaw - LLVM a jakość i bezpieczeństwo oprogramowania
18.11 C++ UG Washington, DC - Q & A / Info Sharing
18.11 C++ UG Bristol - Thomas Guest
18.11 C++ UG Düsseldorf - Lightning Talks
18.11 C++ UG North West/Seattle - CppCon Keynote - Bjarne Stroustrup
18.11 C++ UG Sacramento - Sacramento Area C++, First Meetup
25.11 C++ UG San Francisco/ Bay area - Workshop and Discussion Group
26.11 C++ UG Rhein-Neckar - C++11/C++14 loops of fun
26.11 C++ UG Bremen - C++ User Group
26.11 C++ UG Munich - Lightning Talks
CLion 1.2 is released
CLion 1.2 is released with Google Test support, CMake live templates and variables completion, C++ parser and debugger performance improvements, and many other features on board.
CLion 1.2 is here!
by Anastasia Kazakova
From the article
This release covers various essentials of the software development process: unit testing, writing CMake files, working with version control, general IDE look & feel and beyond. Read on for more details.
It's also aligned with updates for other desktop products that comprise JetBrains Toolbox, that in addition makes CLion available within the All products pack.
New updates of CppHints.com, service of recommendations on C++ programming from PVS-Studio team
New updates of C++Hints, service of recommendations on C++ programming
Changes in CppHints.com
by PVS-Studio Team
We got a lot of positive feedback from our readers and continue developing the C++Hints project. We have also answered two requests, that we saw quite often in the letters:
- The RSS feed is added (http://cpphints.com/rss)
- The up-to-date full list of hints is created at: http://cpphints.com/archive
By this moment we have published the following articles:
- Why incorrect code works
- Don't forget that the loop termination conditions are always evaluated completely
- Undefined behavior is closer than you think
- Visual C++ and wprintf() function
- Use a prefix increment operator (++i) in iterators instead of a postfix (i++) operator
- Avoid using a macro if you can use a simple function
- Don't name functions "empty"
- Hot on the heels
- Make your code more stable
- Insidious VARIANT_BOOL
- Do not compare 'this' to nullptr anymore
- Use the keyword "override" when overriding virtual functions
- Evaluate the string literal length automatically
- Do not use #pragma warning(default:X)
- Table-style formatting (continuation)
- Make sure you work with data in streams the right way
- Delegating constructors make life easier
- Use dedicated functions to clear private data
- Table-style formatting
- Don't spare code lines
- Start using enum class in your code, if possible
- A good compiler and coding style aren't always enough
- When using Copy-Paste, be especially careful with the last lines
- Don't try to squeeze as many operations as possible in one line
- Use the '\0' literal for the terminal null character
- Avoid using multiple small #ifdef blocks
- Beware of throwing exceptions in destructors
- Check all the fragments where a pointer is explicitly cast to integer types
- Do not call the alloca() function inside loops
- Don't Do the Compiler's Job
- Use available tools to analyze your code
- Larger than 0 does not mean 1
- Copy once, check thrice
- Beware of the ?: operator and enclose it in parentheses
An introduction to C++'s SFINAE concept -- Jean Guegant
Jean Guegant describes in a very detailed way different implementation stategies of compile-time introspection of a class member for C++98, C++11 and C++14.
An introduction to C++'s SFINAE concept: compile-time introspection of a class member
by Jean Guegant
From the article:
As a C++ enthusiast, I usually follow the annual C++ conference cppconf or at least try to keep myself up-to-date with the major events that happen there. One way to catch up, if you can't afford a plane ticket or the ticket, is to follow the youtube channel dedicated to this conference. This year, I was impressed by Louis Dionne talk entitled "C++ Metaprogramming: A Paradigm Shift". One feature called is_valid that can be found in Louis's Boost.Hana library particulary caught my attention. This genious is_valid function heavily rely on an even more "magic" C++ programming technique coined with the term SFINAE discovered at the end of the previous century. If this acronym doesn't speak to you, don't be scared, we are going to dive straight in the subject.
Happy Halloween: C++ and zombies
Happy Halloween!
C++ and Zombies: A moving question
by Jens Weller
From the article:
And that there are two fractions, one of them stating, that it is ok to have well defined zombies, while some people think that you'd better kill them...
Meeting C++ is sold out!
Yesterday, the last avaiable ticket for Meeting C++ was sold!
Meeting C++ 2015 is sold out
by Jens Weller
From the article
In the beginning of October I decided to add 50 additional tickets to this years Meeting C++...
Random Acts of Optimization --Tony Albrecht
Discussion regarding systematic approach to go about optimization of logic.
Random Acts of Optimization
by Tony Albrecht
From the article:
The three stages mentioned here, while seemingly obvious, are all too often overlooked when programmers seek to optimize. Just to reiterate:1. Identification: profile the application and identify the worst performing parts.
The solution above is not the fastest possible version, but it is a step in the right direction—the safest path to performance gains is via iterative improvements.
2. Comprehension: understand what the code is trying to achieve and why it is slow.
3. Iteration: change the code based on step 2 and then re-profile. Repeat until fast enough.
Using Variadic Templates cleanly--Florian Weber
Variadics are even more easy to use than we tought:
Using Variadic Templates cleanly
by Florian Weber
From the article:
When one comes across examples for variadic templates, almost always recursion is used to achieve almost everything, for example like this:
// We are lucky: the author correctly used zero // arguments instead of one as the base-case, // thereby avoiding code-duplication: inline void print_to_stream(std::ostream&) {} template<typename Head, typename...Tail> void print_to_stream(std::ostream& stream, const Head& h, const Tail&... t) { stream << h; print_to_stream(stream, t...); }In this article we will see what better alternatives for this rather clumsy hack exist and see how we can write a better version with less code...
Trip report: C++ standards meeting in Kona, October 2015 -- Herb Sutter
Another hour, another trip report from the just-concluded ISO C++ meeting:
Trip report: Fall 2015 ISO C++ standards meeting
by Herb Sutter
See also STL's trip report. The above one goes into more detail on some of the bigger proposals making their way through the standardization process.