------- Comment #4 from pcarlini at suse dot de 2005-10-04 20:53 ------- (In reply to comment #3) > Is there any specific reason that _GLIBCXX_FULLY_DYNAMIC_STRING is not defined > on Cygwin ?
Not having really looked into this issue, the reason is however obvious: the use of _S_empty_rep_storage represents a very good optimization without negative side effects for many (I would say, most) applications of the c++ library. As the string class is currently designed, _GLIBCXX_FULLY_DYNAMIC_STRING should be definitely undefined by default. By the way, for gcc4.1 we will provide an alternate "versatile" string class which doesn't have this problem, but in any case cannot become immediately our default string class implementation due to ABI stability (you can already play with it using CVS gcc: <ext/vstring.h>) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196
