Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-110403

Port away from ushort as char16_t and uint as char32_t

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: P2: Important P2: Important
    • None
    • None
    • None
    • 01ef951c6 (dev), a14bcdfcc (dev), f325bdacb (dev), a849fdc7d (6.5)

      The use of ushort as the scalar type to mean QChar dates back to C++98 when char16_t and char32_t did not exist, yet. Now that they do, use of the C++11 character types yields self-explanatory APIs and less implementation work (casts).

      Acceptance criteria:

      • all Qt APIs that take ushort* or uint* to mean UTF-16 and UTF-32 strings are overloaded with char16_t* and char32_t* alternatives, respectively, and are deprecated according to project standards (some time in the future)
      • all Qt code uses char16_t instead of ushort for UTF-16 character data and char32_t instead of uint for UTF-32 character data.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            cnn Qt Core & Network
            mmutz Marc Mutz
            Vladimir Minenko Vladimir Minenko
            Alex Blasche Alex Blasche
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                There are no open Gerrit changes