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

Resolve QtScript behavior that reflects implementation of old ("classic") back-end

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: P4: Low P4: Low
    • None
    • None
    • Qt Script
    • None

      Parts of the QtScript API and runtime expose behaviors that reflect the implementation of the old (Qt 4.5) back-end.

      It has proven difficult to implement the exact behavior on top of other JavaScript engines, such as JavaScriptCore (JSC) and V8.

      Not all of this behavior is documented, but some of it is.
      The behavior is tested in the QtScript autotests, and a lot of the cases are currently treated on an equal level with the "standard"/"officially sanctioned" behavior.

      This task collects the behaviors in question. The aim is, for each case, to document why the behavior is like that (e.g., freak accident, or is it actually well-thought-out and useful?), and assess the importance of keeping the old behavior (i.e., what is the perceived impact of changing it).

      As an overall goal, we would like the QtScript back-end integration layer to be as thin as possible; this means trying to avoid "magic" code that only serves to satisfy behavior that perhaps nobody relies (or should rely) on.

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

            Unassigned Unassigned
            kenthans Kent Hansen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes