Closed Bug 53209 Opened 24 years ago Closed 24 years ago

eliminate |nsSharedString|

Categories

(Core :: XPCOM, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla0.9

People

(Reporter: scc, Assigned: scc)

References

Details

Attachments

(2 files)

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.
Status: NEW → ASSIGNED
Component: XPCOM → String
Target Milestone: --- → mozilla0.8
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
|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|
This is ready to go, the class was unused by anyone other than the string tests.
Keywords: approval, patch, review
patch checked in
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Keywords: approval, patch, review
Resolution: --- → FIXED
Blocks: 28221
Component: String → XPCOM
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: