Re: [Development] Using semicolons in JS (QML)

2016-10-04 Thread Viktor Engelmann
Am 30.09.2016 um 17:43 schrieb Shawn Rutledge: > Back in Nokia times it was said that we shouldn't use semicolons, > because it would speed up the parsing [...] As someone who has written countless parsers, I *highly* doubt that this is actually true. Indenting with tabs was also believed to be *

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-10-04 Thread Thiago Macieira
Em terça-feira, 4 de outubro de 2016, às 11:03:58 CEST, Edward Welbourne escreveu: > Marc Mutz said: > > Qt 5.6 is C++98-only while 5.7+ is C++11. That means patches that will > > be developed against 5.7+ will very likely have C++11 constructs in > > them that won't work in Qt 5.6. > > Conversel

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-10-04 Thread Konstantin Tokarev
04.10.2016, 14:04, "Edward Welbourne" : > Marc Mutz said: >>  I just came to realise another reason against cherry-picking: >> >>  Qt 5.6 is C++98-only while 5.7+ is C++11. That means patches that will >>  be developed against 5.7+ will very likely have C++11 constructs in >>  them that won't wor

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-10-04 Thread Edward Welbourne
Marc Mutz said: > I just came to realise another reason against cherry-picking: > > Qt 5.6 is C++98-only while 5.7+ is C++11. That means patches that will > be developed against 5.7+ will very likely have C++11 constructs in > them that won't work in Qt 5.6. Conversely, code developed in 5.6 shall

Re: [Development] Managing branches of Qt's git modules

2016-10-04 Thread Oswald Buddenhagen
On Fri, Sep 30, 2016 at 11:39:20AM +0100, Sean Harmer wrote: > just a query as to how people do bulk checkouts of different branches > when working with the Qt git modules. It would be nice to be able to use > git submodule foreach ... but this is a problem because not all modules > use the same

Re: [Development] Using semicolons in JS (QML)

2016-10-04 Thread Simon Hausmann
Hi, When QML used V8 as JavaScript engine and its own expression interpreter called V4 for "simple" expressions, some of these "simplifications" were needed to ensure the bindings could be understood by the simpler evaluator instead of going for a full fledged V8 binding. These assumptions

Re: [Development] Using semicolons in JS (QML)

2016-10-04 Thread Eike Ziller
> On Oct 1, 2016, at 8:33 AM, Olivier Goffart wrote: > > On Freitag, 30. September 2016 15:43:57 CEST Shawn Rutledge wrote: >> Back in Nokia times it was said that we shouldn't use semicolons, because it >> would speed up the parsing and reduce the size of resources slightly. [...] > > Back in