Closed
Bug 74985
Opened 24 years ago
Closed 22 years ago
unify strings under transformix code
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
People
(Reporter: scc, Assigned: jag+mozilla)
References
Details
...once mozilla/string can be built stand-alone, we should do the work needed to
make transformix use those strings instead of their own hand-rolled implementations.
Reporter | ||
Updated•24 years ago
|
Reporter | ||
Comment 1•23 years ago
|
||
re-targeting milestones, starting from a clean slate
Target Milestone: mozilla1.1 → ---
Comment 2•23 years ago
|
||
Oh yes!
Reporter | ||
Comment 3•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
Comment 4•22 years ago
|
||
this bug dies together with the XSLT one. I forgot that we had this one, too.
TransforMiiX standalone is using Mozilla strings now, together with a bunch of
NSPR/XPCOM, so even the standalone build issues are not burning our fingernails
anymore these days. Be gone, days of small trees.
*** This bug has been marked as a duplicate of 74786 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
Component: String → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•