October 25, Pavia, Italy
November 6-8, Berlin, Germany
November 3-8, Kona, HI, USA
By Hartmut Kaiser | Feb 15, 2014 09:04 AM | Tags: c++11 boost
TThe first stable release of the 3.x series of MetaScale’s open-source software is available: NT² 3.0. It also includes its spin-off project, Boost.SIMD (not yet a Boost library). Many Issues have been closed since last beta. The main focus of this release cycle was to fix performances issues and to stabilize some parts of the API.
NT² 3.0 Release Announcement
Source and binary packages can be downloaded here
Full changelog is available here
By Blog Staff | Feb 13, 2014 12:17 PM | Tags: intermediate
Can you spot the bug?
Find the Bug
by Andrzej Krzemieński
From the article:
Today, let's take a short test. Find what is likely to be a bug in the following code and suggest how to fix it.
void Catalogue::populate(vector<string> const& names) { vec_.clear(); vec_.resize(names.size()); for (size_t i = 0; i < names.size(); ++i) vec_[i] = make_unique<Entry>(names[i]); }
By Meeting C++ | Feb 12, 2014 12:51 PM | Tags: undefined behavior standardization numerics networking library issaquah intermediate graphics experimental c++14 advanced
This is the last part in the series for Issaquah, and its the most diverse:
C++ Papers for Issaquah - Library, Graphics, Networking, Numerics & Undefined Behavior
by Jens Weller
From the Article:
The 4th and last part about the C++ Papers for Issaquah. I already covered the first batch of proposals from the Library subgroup in the previous part, now its all about papers from Library, Graphics, Networking, Numerics and Undefined Behavior. A very diverse part.
By Meeting C++ | Feb 11, 2014 03:58 AM | Tags: standardization issaquah intermediate experimental c++14 advanced
The third part of my series about the papers for Issaquah is about the first batch of library proposals
C++ Papers for Issaquah - Library I
by Jens Weller
From the article:
The 3rd part of the C++ papers for Issaquah series will be about the library proposals. The last part covered the papers from concepts, database and evolution. There are a lot of proposals from the library group, and I think some of them are the most interesting, as they don't have any impact on the core language.
By Blog Staff | Feb 9, 2014 08:40 PM | Tags: intermediate basics advanced
As interest in C++ keeps rising, there are more C++ events but they are also selling out faster. C++ Now 2013, Going Native 2013, and C++ and Beyond 2013 all sold out, some six months before the event.
Now C++ Now 2014 has sold out faster than last year -- this time it sold out in less than a month since registration opened, with over three months left to go.
The good news: You can still register to get on the waiting list, and if you act now there's a good chance you can still get a seat. Each year there will be some number of cancellations, and the organizers expect to be able to take a number of people on the waiting list.
If you have not yet registered for C++ Now 2014 but are interested in potentially going, even if you're not certain yet you should join the waiting list today to get in the queue for a chance to sign up for the last few seats that will open up!
If you missed registering for C++ Now and don't make the waiting list, don't despair -- there will be additional major C++ events around the world later this year. Watch for upcoming announcements here on isocpp.org. Stay tuned...
By Blog Staff | Feb 7, 2014 10:47 AM | Tags: None
Quick A: "Inplace" can deal with overlapping ranges, but will take either more space or more time.
Today on StackOverflow:
Difference between
std::mergeandstd::inplace_merge?What is the difference between
std::mergeandstd::inplace_mergein terms of complexity and result when it is executed on two consecutive ranges with elements that are all different ? (I am not a native english speaker and I am not sure to clearly understand what "inplace" means)
By Blog Staff | Feb 7, 2014 09:36 AM | Tags: intermediate
Overload 119 is now available. It contains the following C++-related articles, and more:
Adding parameters to an object can be messy. Here is a description of method chaining -- an interesting way to pass parameters into methods in a more readable fashion.
How confusing does it get when references refer to references and references are captured by value? Pete Barber shows us that it all falls out in the C++ consistency wash.
By Meeting C++ | Feb 6, 2014 04:33 PM | Tags: standardization issaquah intermediate experimental evolution database concepts advanced
This is the second part of my series about the papers for the next C++ committee meeting in Issaquah:
C++ Papers for Issaquah - Concepts, Database & Evolution
by Jens Weller
From the article:
This is the second part about the papers for the C++ committee meeting in February in Issaquah. This time featuring papers from the subgroups of concept, database and evolution. Again, most papers in this series aim for a standard after C++14, most important for C++14 will be the national comments on the new standard. Also there are no new papers from the core working group, only the active issues, defects report and closed issues report are on this mailing.
By Blog Staff | Feb 6, 2014 05:39 AM | Tags: None
Recently on StackOverflow:
Why does unique_ptr take two template parameters when shared_ptr only takes one?
Both
unique_ptrandshared_ptraccept a custom destructor to call on the object they own. But in the case ofunique_ptr, the destructor is passed as a template parameter of the class, wherease the type ofshared_ptr's custom destructor is to be specified as a template parameter of the constructor.template <class T, class D = default_delete<T>> class unique_ptr { unique_ptr(T*, D&); //simplified ... };and
template<class T> class shared_ptr { template<typename D> shared_ptr(T*, D); //simplified ... };I can’t see why such difference. What requires that?
By Blog Staff | Feb 5, 2014 03:12 AM | Tags: basics
Quick A: Something cool and convenient -- you can construct a temporary variable of the parameter type without having to repeat the type.
From SO:
C++ 11 Curly Braces
I haven't used C++ for a good few years, and have just come across this:
program.build({ default_device })The definition is:
cl_int build( const VECTOR_CLASS<Device>& devices, const char* options = NULL, void (CL_CALLBACK * notifyFptr)(cl_program, void *) = NULL, void* data = NULL) constWhat are the curly braces there for? I have never seen them used in a function call like this before. I assume it has something to do with the function pointer, but that seems optional?