Mozilla 2/Strings: Difference between revisions
Jump to navigation
Jump to search
(link up analysis passes) |
m (Link up the analysis bug) |
||
| Line 14: | Line 14: | ||
= Status = | = Status = | ||
This is still in the phase of collecting data and experimentation. | This is still in the phase of collecting data and experimentation. See {{bug|416411}}. | ||
* [[Mozilla 2/Strings/Dynamic Analysis]] | * [[Mozilla 2/Strings/Dynamic Analysis]] | ||
Latest revision as of 20:29, 8 February 2008
Owners
bsmedberg, dmandelin
Summary
We know we pay a fair price for string handling across the XPConnect boundary. We also know that the Mozilla string classes are a major barrier to entry for new hackers. The goals of a string overhaul for Mozilla 2 are to:
- share a common string class across the DOM/XPCOM and the JS engine
- reduce the complexity of manipulating string
In addition, we will need to make a decision about character encodings in Tamarin (currently UTF8, from Spidermonkey UCS2)... this is an unknown apart from the XPCOM string work.
Status
This is still in the phase of collecting data and experimentation. See bug 416411.
Risks and Assumptions
This is a big rewrite, and it is not easy to create a rewrite which is correct in all cases as well as still produces readable code.