Closed
Bug 53209
Opened 25 years ago
Closed 25 years ago
eliminate |nsSharedString|
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla0.9
People
(Reporter: scc, Assigned: scc)
References
Details
Attachments
(2 files)
|
3.00 KB,
patch
|
Details | Diff | Splinter Review | |
|
2.10 KB,
patch
|
Details | Diff | Splinter Review |
Now that we have a common underlying sharable buffer scheme ... |nsSharedString|
should exploit it to the fullest extent possible; though after the introduction
of copy-on-write strings, I imagine |nsSharedString| will be deprecated, hmmm.
|
Assignee | |
Comment 1•25 years ago
|
||
|
|
Assignee | |
Updated•25 years ago
|
Status: NEW → ASSIGNED
|
|
Assignee | |
Updated•25 years ago
|
Component: XPCOM → String
Target Milestone: --- → mozilla0.8
|
|
Assignee | |
Comment 2•25 years ago
|
||
this may not need to be done at all, if |nsSharedString| goes away in favor of
|nsInternString|. Delaying this to 0.9 will let us find out before we throw
away any work.
Target Milestone: mozilla0.8 → mozilla0.9
|
|
Assignee | |
Comment 3•25 years ago
|
||
|nsSharedString| isn't being used, and that may be one of the two good names for
the copy-on-write string described in bug #53065 (the other being
|nsCommonString|. So I'm actually just going to eliminated |nsSharedString|
from the build. Changing summary accordingly.
Summary: re-factor |nsSharedString| based on the new sharable buffer code → eliminate |nsSharedString|
|
|
Assignee | |
Comment 4•25 years ago
|
||
|
|
Assignee | |
Comment 5•25 years ago
|
||
This is ready to go, the class was unused by anyone other than the string tests.
|
|
Assignee | |
Comment 6•25 years ago
|
||
patch checked in
|
||
Updated•5 years ago
|
Component: String → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•