Location visible to members
RSVPs for this event are now closed! If theory and practice mesh - we should be able to accommodate everyone who has RSVPd here and/or through IEEE vtools (without violating fire code).
Please: see the update regarding timing, and the importance of arriving well before 7:00 PM to get your car in before the National Instruments security gates close. If you are late, you won't be let in...sorry we found out this was an issue. Be there at 6:00 sharp if you can.
Also: it may be good to bring a laptop or tablet to follow along with the slides...as given the number of people, some might be sitting pretty far back from the projector during the talk. We're attempting to get a second display set up a bit further back.
The rumors are true: Bjarne Stroustrup (http://en.wikipedia.org/wiki/Bjarne_Stroustrup) is coming to Austin to speak! IEEE is hosting him, but they've opened up the event to our group and others who would like to attend.
Bjarne will be covering some of how to apply C++11 to achieve his vision of "Modern C++". He offers this description of the presentation:
"We know how to write bad code: Litter our programs with casts, macros, pointers, naked new and deletes, and complicated control structures. Alternatively (or in addition), obscure every design decision in a mess of deeply nested abstractions using the latest object-oriented programming and generic programming tricks. For good measure, complicate our algorithms with interesting special cases. Such code is incomprehensible, unmaintainable, usually inefficient, and not uncommon.
But how do we write good code? What principles, techniques, and idioms can we exploit to make it easier to produce quality code? I will make an argument for type-rich interfaces, compact data structures, integrated resource management and error handling, and highly-structured algorithmic code. I will illustrate my ideas and motivate my guidelines with a few idiomatic code examples.
I will use C++11 freely. Examples include auto, general constant expressions, uniform initialization, type aliases, type safe threading, and user-defined literals. C++11 features are only just starting to appear in production compilers, so some of my suggestions have the nature of conjecture. However, developing a 'modern style' is essential if we don’t want to maintain newly-written 1970s and 1980s style code in 2020.
This presentation reflects my thoughts on what 'Modern C++' should mean in the 2010s: a language for programming based on light-weight abstraction with a direct and efficient mapping to hardware, suitable for infrastructure code."
Looking forward to it! Meeting agenda follows:
6:00 p.m. Networking and Gathering
(PLEASE ARRIVE TO THE EVENT WELL BEFORE 7:00, AS THE NATIONAL INSTRUMENTS SECURITY GATES CLOSE AT THAT TIME. YOU WILL NOT BE ABLE TO GET YOUR CAR IN IF YOU ARE LATE. IDEALLY BE THERE AT 6:00 SHARP IF YOU CAN!)
--- 7:00 p.m. Call to Order, Announcement 7:15 p.m. Presentation, with Q/A 8:45 p.m. Meeting Evaluation, Adjourn