[Webkit-unassigned] [Bug 6068] New: DOMStringImpl needs to be beefed up in preparation for removing QString

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=6068

           Summary: DOMStringImpl needs to be beefed up in preparation for
                    removing QString
           Product: WebKit
           Version: 412+
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: NEW
          Severity: normal
          Priority: P4
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: macdome at opendarwin.org


DOMStringImpl needs to be beefed up in preparation for removing QString

One of our eventual goals is to remove the use of QString throughout our engine.  Currently we have at 
least 3 common string classes in WebCore: UString (UTF16), DOMString (UTF16), and QString (UTF8).  We 
do some operations using each.  Conversions between the three can be painful.  Most painful however is 
the repeated conversion between DOMString and QString, as we have to pay the UTF16<->UTF8 encoding 
change cost every time.

One of the eventual goals is to remove the use of QString and instead use DOMString or DOMStringImpl 
(wrapped in a SharedPtr).  This bug tracks that progress.

-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.