To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=75224
                 Issue #|75224
                 Summary|RFE: ::rtl::OUString should allow in-place replacement
                        | of characters
               Component|framework
                 Version|680m202
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P3
            Subcomponent|code
             Assigned to|sb
             Reported by|fs





------- Additional comments from [EMAIL PROTECTED] Thu Mar  8 09:06:28 +0000 
2007 -------
Currently, OUString's various replace flavours always return a new string,
created as copy of the original string, plus replacements. This is a waste of
resources in (common) cases such as
  sName = sName.replace( '/', '_')
where the replacement is really to be happen in-place.

Given that the (deprecated by the new coding guidelines) tools-based string
offers in-place replacement, the rtl-based OUString should do so, too.

Note: While we are at it: There are some more methods which deserve an overhaul
in this respect. In particular, toAsciiUpper/LowerCase and trim also might,
sometimes, be needed as in-place version, though this is more seldom than for
replacements.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to