Closed
Bug 70078
Opened 24 years ago
Closed 24 years ago
un-templatize string base classes
Categories
(Core :: XPCOM, defect, P2)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla0.9
People
(Reporter: scc, Assigned: scc)
References
Details
since we're only specializing on exactly two types, templatization was always
just a convenience, not a necessity; and frankly, it hasn't been that
convenient. I suspect Solaris builds and other 2.7.2.3 systems will become less
build-fragile if I un-templatized the abstract base classes for strings.
Targeting mozilla0.9.1, but this is one I'd like to pull into mozilla0.9 if I
have time
| Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla0.9.1
| Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9
| Assignee | ||
Comment 1•24 years ago
|
||
since this bug now blocks 70142, I don't have to hang it from the top dependency
bugs
| Assignee | ||
Comment 2•24 years ago
|
||
this has been checked in on the STRING_081_BRANCH; when the branch is merged
into the trunk, I'll close this bug
| Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.8.1 → mozilla0.9
| Assignee | ||
Comment 3•24 years ago
|
||
(mass change) didn't get these in for target milestone mozilla0.8.1 but they are
very close. Moving all to mozilla0.9.
| Assignee | ||
Comment 4•24 years ago
|
||
landed the branch; fix checked in. The string classes are, for the most part,
un-templatized. At this time, buffer handles and |nsPrivateSharableString| are
still templatized ... if that proves to be a problem, un-templatizing them
should only take a few minutes.
| Assignee | ||
Comment 5•24 years ago
|
||
and marking fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Component: String → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•