Perhaps we were not on the same page. What I meant was as long as std::string is used as either the source or target of a lexical_cast, thread safety may not be guaranteed (due to lack of a guarantee by std::string). Though weird/bad things happen more frequently under heavy load and/or on multiprocessor (hyperthreading included) machines. On 8/28/06, Gennaro Prota <gennaro_prota@yahoo.com> wrote:
On Sun, 27 Aug 2006 18:37:49 -0700, "Gregory Dai" <gregory.dai@gmail.com> wrote:
That's not true. std::basic_string<T> is not thread safe. I spent couple months early this year to deal with that fact and finally came up with an alternative string class with the same interface as std::string but does not use the copy-on-write technique.
Did you think it had a dynamically allocated buffer _on the stack_? Where do you hold the characters of *your* string class instances? C'mon.
-- [ Gennaro Prota. C++ developer, Library designer. ] [ For Hire http://gennaro-prota.50webs.com/ ]
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Thanks, Greg