Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-20885 Larger changes for Qt 5
  3. QTBUG-23564

Qt should use C++11 features (with macro guards) in existing APIs.

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Not Evaluated
    • Resolution: Done
    • Fix Version/s: 5.0.0
    • Component/s: None
    • Labels:
      None
    • Technical Risk:
      Normal

      Description

      If Qt starts using, for example, the final specifier on classes that are not intended to be inherited or on classes that are not intended to be overridden, then for 3rd parties doing those newly forbidden things (while already using c++11 in their build flags) it would be a source incompatible change.

      We should evaluate if any scenarios like that are real-world enough, and see if any action can be taken.

        Attachments

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

          Activity

            People

            Assignee:
            laknoll Lars Knoll
            Reporter:
            stephen.kelly Stephen Kelly (Unused account) (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes