From: Dean M. B. <mik...@gm...> - 2010-10-21 05:00:59
|
On Thu, Oct 21, 2010 at 3:01 AM, Nelson, Erik - 2 <eri...@ba...> wrote: >> Kim Gräsman wrote on Wednesday October 20, 2010 2:41 PM > >> Microsoft's STL as of VS2008 doesn't use COW, it uses the small-string >> optimization. Not sure if they went (back?) to COW in 2010, but I >> doubt it. >> >> LLVM has an interesting sub-project implementing a standard library >> from scratch, and one of the decisions they mention in the overview is >> using small string optimization over COW, as if it was a plain truth; >> http://libcxx.llvm.org/. >> >> So, I think there's merit to not expecting COW from std::string. >> > > STLPort (ships with Sun C++ compilers) doesn't use COW, either. > > http://stlport.sourceforge.net/ > > and the links I put in a previous post > > http://bit.ly/hiqqU > http://bit.ly/cqpKVN > > have indications in the discussions that gcc may move away from COW > in the future. > Yep. > Visual Studio 6.0 had well-known thread-safety bugs in its COW > std::string implementation, and was the last version of MSVC to > use COW, according to my understanding. > > http://support.microsoft.com/kb/813810 > http://www.eggheadcafe.com/software/aspnet/32308437/-thread-safe-stl-for-vc60.aspx > Ah, I stand corrected then. :) That's good to know, I'll fix that most probably in 0.9 -- unless someone else beats me to it and sends a pull request for 0.8-devel. :) -- Dean Michael Berris deanberris.com |