Hi Bjoern, > // better solution > aResult = ::some_namespace::replaceString( > aResString, aReplacementStr, String::CreateFromInt32( nMyNumber )); > > I don't think we need to have this as a method at the OUString (the > interface is already quite big).
Well, whether this is part of the OUString class, or in some external helper namespace/class, is a matter of taste, religion, and other things hard to debate about ;) Personally, I'd prefer to have a OUString member, but that might be only me. I'd buy the OUString-external helper, too. On the other hand ... replacement might be cheaper (yes, I'm doing optimizations here before I proved I need them - which of our coding guideline items is viloted here?) if it can be done in-place. That could save those costly memory allocations, at least somtimes. (Which, btw. is a reason why I don't like OUString's constness-paradigmn.) Which would mean we should have the functionality at the OUStringBuffer. Would also be nice to have, but then Stephan should be prepared for me submitting RFEs for the OUStringBuffer usability :) 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]
