Closed
Bug 82456
Opened 23 years ago
Closed 15 years ago
short term: make |ReplaceSubstring| use |nsSubstituteC?String|, long term: eliminate |ReplaceSubstring|
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: scc, Assigned: jag+mozilla)
References
Details
The machinery is in place to eliminate |ReplaceSubstring|, as per bug #75164.
Let's turn |ReplaceSubstring| into a one-liner that uses |nsSubstituteC?String|
to do its job. For the long term, let's start advocating direct use of
|nsSubstituteC?String| (or else a helper function that produces instance of that).
Reporter | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.2
Reporter | ||
Comment 4•23 years ago
|
||
I'll want to profile the effect of this change before I check it in.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Comment 5•23 years ago
|
||
looks like we could live without these for 0.9.4. let me know if this is a
mistake. moving out...
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Comment 6•23 years ago
|
||
0.9.5 is out the door. bumping TM up by one.
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Comment 7•23 years ago
|
||
Too late for 0.9.6, this needs retargeting.
Comment 8•23 years ago
|
||
unsetting target milestone until we get a good one.
Target Milestone: mozilla0.9.6 → ---
Reporter | ||
Comment 9•22 years ago
|
||
giving up ancient string bugs to the new string owner. jag, you'll want to sort
through these and see which ones still apply and go with or against the
direction in which you intend strings evolve
Assignee: scc → jaggernaut
Status: ASSIGNED → NEW
Updated•15 years ago
|
QA Contact: scc → string
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Updated•4 years ago
|
Component: String → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•