[prev in list] [next in list] [prev in thread] [next in thread]
List: icu-bugrfe
Subject: Notification: incoming/1730
From: jtcsv () jtcsv ! com
Date: 2002-02-26 21:10:29
[Download RAW message or body]
ICU bug tracking authorized access notification
schererm moved PR#1730 from incoming to others
Message summary for PR#1730
From: markus.scherer@jtcsv.com
Subject: need UnicodeString::clone() for thread-safe string handling
Date: unknown
0 replies 0 followups
Notes: assigned to markus
target: 2002q1
====> ORIGINAL MESSAGE FOLLOWS <====
From: markus.scherer@jtcsv.com
To: jtcsv@jtcsv.com
Subject: need UnicodeString::clone() for thread-safe string handling
Full_Name: Markus Scherer
Version: 200
OS: all
ICU_Component: others
project: ICU4C
Submission from: (NULL) (32.97.110.69)
Submitted by: schererm
Currently the only way to make sure that a copy of a UnicodeString can be used
concurrently to the original is to
if(s.length()>0) {
s.setCharAt(0, s.charAt(0));
}
We need a clone() function that is slightly smarter. For example, it should not
copy the buffer if the string is a read-only alias.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic