Closed Bug 76334 Opened 24 years ago Closed 15 years ago

[tracking bug] |GetFragment| and iteration work

Categories

(Core :: XPCOM, defect)

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

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: scc, Assigned: jag+mozilla)

References

Details

This is a tracking bug to manage work I need to do to unify
|GetReadableFragment| and |GetWritableFragment|; upgrade fragments to buffer
handles; get the |const| story straight; and fix iteration over complicated
aggregate strings, e.g., concatenations of substrings of concatenations.  This
work is all related by it's nearness to the fragment machinery.
Status: NEW → ASSIGNED
Blocks: 70090
Depends on: 73050
Depends on: 70083
Depends on: 70082
Depends on: 74709
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
Fragments are gone.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Component: String → XPCOM
You need to log in before you can comment on or make changes to this bug.