Closed
Bug 195008
Opened 22 years ago
Closed 22 years ago
Improve performance of nsICollation::CompareString
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
RESOLVED
DUPLICATE
of bug 207634
People
(Reporter: nhottanscp, Assigned: nhottanscp)
Details
Attachments
(1 file)
The current implementation of nsICollation::CompareString generates two
collation keys for a comparison. It can be inefficient because the comparison
may not require a whole string to be transformed to a collation key (e.g. may
unmatch at the first character).
As we use OS API to generate collation keys, we may also use OS API for
comparing string which might do that kind of optimization.
|
Assignee | |
Comment 1•22 years ago
|
||
|
|
Assignee | |
Updated•22 years ago
|
Attachment #117753 -
Flags: review?(ftang)
|
||
Comment 2•22 years ago
|
||
I've implemented something fairly similar for bug 207634 because I needed to get
rid of nsCollation::CompareString
|
|
||
Comment 3•22 years ago
|
||
*** This bug has been marked as a duplicate of 207634 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
|
||
Updated•21 years ago
|
Attachment #117753 -
Flags: review?(ftang)
You need to log in
before you can comment on or make changes to this bug.
Description
•