Hi, while browsing around I found the following piece of info:
strstream considered harmful There exists a deprecated class similar to stringstream that is called strstream. Do not confuse these two classes. They are not the same. strstream has a very error prone interface because of the way it handles memory. One problem is that it does not append trailing nulls when str() is called. So you must append a trailing null, or std::ends. Another important thing to remember is that if you use ostrstream with a dynamic buffer, like this: std::ostrstream strout; strout << "The answer is ... " << 42 << std::endl << std::ends; strout.str(); Then calling str has the peculiar side effect that the caller is responsible for managing the memory allocated by strout's buffer, which is pretty silly since the caller does not know how the memory was allocated (it may be allocated using malloc() or new). So to make the stupid thing take its memory back, one makes the following call: strout.freeze(0); It's worth mentioning that there is another, safer way to use ostrstream and that is to use it with a static buffer. If you do this, you don't need to deal with this freeze() nonsense. To do this, call the constructor that takes a character array as an argument. char a[100]; std::ostrstream strout(a,100); strout << "the answer is" << 42 << std::endl << std::ends; std::cout << a << std::endl;
I noticed there are some places that use strstream. Should we depreciate the use of it for FlightGear? Eirik _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
