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)

Product:
Core
Component:
XPCOM
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
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).
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.2
*** Bug 74904 has been marked as a duplicate of this bug. ***
*** Bug 74896 has been marked as a duplicate of this bug. ***
*** Bug 43509 has been marked as a duplicate of this bug. ***
I'll want to profile the effect of this change before I check it in.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
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
0.9.5 is out the door. bumping TM up by one.
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Too late for 0.9.6, this needs retargeting.
unsetting target milestone until we get a good one.
Target Milestone: mozilla0.9.6 → ---
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
QA Contact: scc → string
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Component: String → XPCOM
You need to log in before you can comment on or make changes to this bug.