Interested in C++ present and future? Want to improve your skills and knowledge - or just hang out with like-minded individuals? Don't miss this month's C++ London meetup!

18:30 pre-session networking/ drinks and think-cell sponsored food

19:00 Phil Nash << "Hello World"

Brief introduction and raffle for a JetBrains license

19:10 Arno Schödl<< "Why Iterators Got It All Wrong — and what we should use instead"

Want to learn about Foreign Function Interface? Join Jonathan Coe at this months C++ London to find out more!

It uses libclang and (lightly) annotated C++ to generate interfaces in Python, Ruby, Lua...

It's an open source project in early development, I'll show how it works, how it can be extended and how object lifetime management is handled.

You understand iterators, right? How would you describe them? "Iterators are used to point into sequences of elements." Sounds good?

More recently, the concept of ranges has been introduced to mean anything that exposes iterators. In particular, ranges include range adaptors for lazily transforming or filtering sequences of elements, and they, too, have iterators. All good? Unfortunately, no. The iterator concept, which we have been using since the advent of C++, is fundamentally flawed. In particular, some iterators must behave differently depending on whether they are meant to point at an element or at a boundary between elements. So elements and boundaries are really two distinct concepts. In this talk, I will convince you that the problem is real and has practical implications, make a proposal on how to fix it and show how the solution not only fixes the problem but makes for clearer code and prevents mistakes.