Closed
Bug 46892
Opened 24 years ago
Closed 15 years ago
make |nsStr| and other obsolete string implementation go away
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dougt, Assigned: jag+mozilla)
References
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
When looking at nsStr::Destroy(), (mCapacity - mLength), on the average, is 54
bytes.
Reporter | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
Note, though, that |nsStr| as a class is going away altogether. Strings are soon
to be allocated at exactly the correct size and grown for operations that fault
on space. User calls to set the capacity will be honored exactly.
Status: NEW → ASSIGNED
Reporter | ||
Comment 3•24 years ago
|
||
if that is the case, this bug will become invalid
Comment 4•24 years ago
|
||
This would be a lot more useful if it disregarded cases where the nsStr is part
of an AutoString. The waste there is just not a problem.
Comment 6•24 years ago
|
||
nsStr is soon to go away entirely; I'll mark this bug fixed at that time
Component: XPCOM → String
OS: Windows NT → All
Hardware: PC → All
Summary: nsStr wastes on the average of 54 bytes → make |nsStr| go away
Target Milestone: --- → mozilla0.9.1
Updated•24 years ago
|
Updated•24 years ago
|
Updated•24 years ago
|
Updated•24 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9
Updated•24 years ago
|
Target Milestone: mozilla0.9 → mozilla1.1
Comment 8•23 years ago
|
||
re-targeting milestones, starting from a clean slate
Target Milestone: mozilla1.1 → ---
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: doug.turner → string
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Updated•4 years ago
|
Component: String → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•