On Wed, Mar 6, 2013 at 7:23 PM, Alan Alpert <[email protected]> wrote:
> The problem with a warning on the console is that these are emitted > every time the application runs. So if you've written your application > correctly and are happy with it, the user shouldn't be seeing the > console flooded with warnings. This is why QML needs to be > conservative with the compile warnings, compared to C++, they should > all be considered runtime warnings. > setPermissive/setVerbose like method for the interpreter maybe? That could be useful for the development process for instance, and not just for this case, i.e. more like in general about getting verbose warnings about potential places that can cause bugs. They could check such a verbose output before publishing the application or so. Laszlo
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
