On quarta-feira, 27 de julho de 2016 11:47:03 PDT BogDan Vatra wrote: > On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote: > > Op 27/07/2016 om 09:53 schreef BogDan Vatra: > > Would that not break existing QML applications that now use enums backed > > by scoped enums in C++? > > It will, but personaly I can't see a better solution ...
I have already said what to do: make it an opt-in on registration of the enum to the QML/JS engine. > So, either we break the existing QML apps that used scoped enums in C++ > (which is useless, because in QML side you'll get name clashing) or we keep > it as it is now and never "fix" it. I'd like the first option :). I really hate it. Breaking applications should not even be an option on the table. Let's start with "we won't gratuitously break applications" and work to find a solution from there. > Of course if we can find a better solution to have them both is even better > ! -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
