Hi All - Just a quick note to let everyone know that Boost has been assigned 10 SOC projects! This is more than we expected and I'm hopeful will result in some great work. Even so, there are many excellent students and projects that applied for Boost projects and were NOT selected. The competition for these 10 slots was quite brutal. The choices were extremely difficult to make. It was often very hard to decide between a totally novel, high risk, project proposal and a fairly straight-forward extension to a current library. As you'll see, we ended up with some of both. The mentors have been trying to reach everyone with a notification one way or another, but it's a large list. All applicants should have heard from Google by now. If you have questions you can post to boost_soc2006@crystalclearsoftware.com and someone should get back to you. I'm not going to publicy share the details of the list just yet -- until we are sure all the administrative items are confirmed (google apparently accidently informed 1800 people they were accepted and then had to retract). Eventually the list should show up here: http://code.google.com/soc/boost/about.html Jeff
Hi! I came up with a I/O weird behaviour with boost::tuple. In the following example program: #include <boost/tuple/tuple.hpp> #include <boost/tuple/tuple_io.hpp> #include <iostream> #include <sstream> int main() { using namespace std ; using namespace boost ; typedef ::boost::tuple< float > tuple_type ; float v ; tuple_type t ; string str = "0.1" ; istringstream str_in( str ) ; str_in >> v ; if ( str_in >> t ) { cout << "yes " ; } else { cout << "no " ; } cout << t << endl ; return 0 ; } I expect the output to be "no (0)", but I get "yes (0)". Usually, I expect operator>> with streams to change the state of the stream to some kind of failure state if it could not read the requested type. For example if I replace the 'if' with the following: if ( str_in >> t.get< 0 >() ) then I get "no (0)". Although I know it is not the equivalent to reading the tuple t directly (no open/close character), at least I get the error set I as expected. If the end of input (eof) as been read before reading the tuple, then the condition will be false. So, I am wrong to expect such a behavior? Or is there a bug here (either in the way I use it or in the tuple's input operator)? If it matters, the compiler used is g++ 4.0. Thanks, -- François Duranleau LIGUM, Université de Montréal "Do you want to use a machine, or do you want the machine to use you?" - Doohan, in _Cowboy Bebop_
participants (2)
-
François Duranleau -
Jeff Garland