Hi Stephan, > Issue 75224 argues in favor of mutable rtl::OUString with (alleged) > resource wastage. However, without actual measurements, it is hard to > tell whether that really is something we need to address.
Being the one who submitted the issue, let me rephrase: That's definately resource wastage, as code like sName = sName.replace( '/', '_' ) does an unnecessary allocation of memory (in case the previous pData member is not shared, if course). Admittedly, whether this is a serious and noticable waste is another question :). Also, we'll have a hard time convincing people to abandon the tools-based string (as is required by the coding guidelines) if the to-be-substitute doesn't offer the same convenience. Admitted, it's not too difficult to really write "sName = sName.replace" instead of "sName.replace". But IMO, the current behaviour is not expectation-conformant, even more for people being used to the old string (nearly everybody whose daily work happens above the UDK, I'd claim). Personally, I always need to code this line twice, because in the first attempt, I forget the assignment, and wonder that it's not working ... Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
