On Wed, Dec 12, 2012 at 5:06 PM, Chris Adams <chris.ad...@qinetic.com.au> wrote: > Hi, > ... >> Since this is currently necessary, it does mean that anyone who wants >> to see enums properly supported should help out with the v4vm work >> (currently the best way to fix QTBUG-24799). > > > The v4vm implementation is an orthogonal issue entirely. Let me put it this > way: this "unresolvable typename" issue existed in 4.x when we used JSC, and > it exists in 5.0 now that we're using V8, and it will exist in 5.1 or 5.2 > when we use v4vm. The problem is an issue with QML's typesystem, not the > JavaScript engine which we use. Unless you're saying that the v4vm effort > also involves improving the typesystem for performance or other reasons > (which is entirely possible, I haven't looked into it too deeply yet, > unfortunately).
You're right it's not the exact same thing. I was more thinking about how if I was going to fix it (and I don't have time right now) I'd do v4vm first expecting that to make it easier to implement enums. -- Alan Alpert _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
