Will this year use the C++11 standard library?
 

I was browsing msdn and watched this talk by Herb Sutter where he talks about changes to the standard library wherein its revealed that const objects are expected by the standard library to be thread safe, and so if our own classes do not follow the same behavior but use the standard library, then I could be subject to some race conditions.

Will we be using the C++11 standard library this year?

Video summarized by StackOverflow here.

Re: Will this year use the C++11 standard library?
 

I think that the version of WindRiver we have is using GCC 3.2, but full C++11 support isn't available in even the latest version of GCC (C++0x/C++11 Support in GCC), so I don't think it will change anything.

Re: Will this year use the C++11 standard library?
 

Highly unlikely. It wasn't involved in the C++ beta, so it's probably not going to be in the final package

Re: Will this year use the C++11 standard library?
 

Search the forums, someone got a GCC 4.x toolchain working for vxWorks, so you could use that if you wanted the newest standard library stuff.

Re: Will this year use the C++11 standard library?
 

rbmj and anyone who he has taken code from have done most of the work. I've just made some small changes and bugfixes to the build system, particularly for building WPILib.

Here's the latest thread on the topic if you're interested!
http://www.chiefdelphi.com/forums/sh...d.php?t=109385

Re: Will this year use the C++11 standard library?
 

I got code from AustinSchuh, Ross Light, and Cody Schafer. The initial code and concept is all to the credit of Austin Schuh. Ross Light did some initial work on this base to make it more configurable, and Cody Schafer added several patches to enhance the support. He also updated the patches to work with 4.7 and found several new issues. After much negotiating I was able to get the effective equivalent of the patches into GCC itself as part of the fixincludes subsystem, and I corrected an issue with the installation header paths with the current build scripts. Though I still have one bug open against GCC, most of the hard work is finished and now it's the tedious maintenance that has to be done.

Felt like they deserved to be called out since they did all the heavy lifting of actually getting a working compiler, in the dark ages of the project when it wasn't clear if it was actually going to be a feasible amount of effort or not...

Anyway, I have compiled binaries on my system. Once I've completed testing and got WPILib up and running I'll post the results. They will be targeted at debian unstable aka testing aka wheezy, but they should be fine on any deb-based distro, and alien might work for rpm-based distros (which can of course still do a manual build).

Everything should be ready for release NLT Saturday, so if you want to play around with it there should be plenty of time during build season to do so :)

EDIT: Used real names instead - they're available from all of their github pages anyway...

Re: Will this year use the C++11 standard library?
 

Not meaning to thread-jack, but do you mind sharing where you got the source for WPILib without installing WindRiver Workbench? The SVN repository doesn't seem to allow for anonymous access and everything I've found telling people how to get source assumes that you have a working WindRiver installation, and I don't have a Windows machine readily available to set that up.

Re: Will this year use the C++11 standard library?
 

Download the workbenchupdate.exe file off of firstforge, change the extension to .zip, extract it, and look around. There should be a wpilib source folder. Learned that trick from the ucpp scripts :)

Re: Will this year use the C++11 standard library?
 

The C++ Update is just a self extracting zip file. You can use almost any unzip tool to get to the source archive inside.

Re: Will this year use the C++11 standard library?
 

FYI: Binaries are available now. See the thread in the global programming forum.