During the last few weeks I got interested in the Google Summer of Code (GSoC), as I did read some emails on the boost mailing lists about it. The Google Summer of Code is for a lot of open source projects an important opportunity to improve and extend their code base, and in 2014 it happens for the 10th time!
I just finished a little tool, which needs to crawl websites, in this case mostly blog posts to extract a few fields. I have been working with QtWebkit for this purpose for a while, one larger project I am working on needs it to index certain websites...
I've written earlier this year about smart pointers in C++, today I just would like to write a little more about shared_ptr. Especially about addiction to shared_ptr, and why you should use unique_ptr in C++11.
The 4th and last part about the C++ Papers for Issaquah, where the C++ committee meets this week. 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.
In february the C++ committee is going to meet for a week in Issaquah, it could be the final Meeting for C++14, the papers in this series will reflect both, C++14 and the standard that will come after it...
My last blog post in 2013 was about the pointer in C++, and how most of it's daily usages in C++ is now being replaced by classes replacing or managing the pointer. The last, the RAII like objects called smart pointers is the topic of this post. I want to give an overview over the choices one can make when using smart pointers.
The last weeks after Meeting C++ 2013 I've been thinking a lot about C++, and also a little bit about pointers. While C++11 brought only little changes for pointers (nullptr f.e.), the semantics and usage of pointers in C++ has changed over the last years.
Meeting C++ 2013 was a blast, and for me a huge success. With over 200 people visiting the conference, it was a lot bigger then last years conference! With 21 Talks in 3 Tracks and 2 keynotes, the conference has evolved into a format, which I'd like to keep for the coming years.
Some parts of the Standard Library in C++11 are predated in boost. When playing around with C++11, you get used to using some parts in the Standard Library that are used in C++03 with their boost counterpart. Also, there is some libraries now occuring, which are C++11 based, so interfacing with either boost or C++11 code is soon an issue.
This is the fourth and last part of the series, which will finalize the Chicago papers for C++14 and beyond. It was again fun reading all the papers, but a lot less papers this time. While writing those lines C++14 is close to its final ways, it seems that the Chicago Meeting is really getting close...