Re: [Development] Feature Freeze Exception: QStringView

2017-02-02 Thread Marc Mutz
On Friday 03 February 2017 08:49:24 Marc Mutz wrote: > Results on GCC 6.1.1, compiled with the same settings as our tests: Better-formatted version posted in comment to https://codereview.qt-project.org/143763 -- Marc Mutz | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group

Re: [Development] Feature Freeze Exception: QStringView

2017-02-02 Thread Marc Mutz
On Friday 03 February 2017 08:00:16 Philippe wrote: > On Thu, 02 Feb 2017 23:52:26 +0100 > > Kevin Kofler wrote: > > > On Tuesday 31 January 2017 15:24:18 Philippe wrote: > > >> I just want to highlight, that QStringView is not COW friendly. AFAIK. > > > > That alone makes it actually a pessimiz

Re: [Development] Request moving project to playground area

2017-02-02 Thread Hamed Masafi
> What are the advantages of NUT/ORM over existing, proven technologies like > ODB? Odb is other than QtSql module, but Nut use Qt so is familiar to Qt developers. Odb has own compiler for pre-compiler declaratives and is hard to use for beginners. But Nut use macro hack and no need another tool fo

Re: [Development] Feature Freeze Exception: QStringView

2017-02-02 Thread Philippe
On Thu, 02 Feb 2017 23:52:26 +0100 Kevin Kofler wrote: > > On Tuesday 31 January 2017 15:24:18 Philippe wrote: > >> I just want to highlight, that QStringView is not COW friendly. AFAIK. > > That alone makes it actually a pessimization. This is why Thiago commented with: >But we still have to

Re: [Development] Feature Freeze Exception: QStringView

2017-02-02 Thread Marc Mutz
On Thursday 02 February 2017 23:52:26 Kevin Kofler wrote: > > But that's why we'll have QStringView Level 3, where only the QStringView > > QLabel::setText() overload will be compiled in. Then, we compile Qt with > > either level and check the respective performance of the result. I'll > > wager th

Re: [Development] Request moving project to playground area

2017-02-02 Thread Kevin Kofler
Hamed Masafi wrote: > This project currently... : > - has code name 'Nut' and suggested name is ORM. But it may have any > other name. ORM is way too generic a name. It needs to be called at least QORM or QtORM or ORM-Qt or something, if you cannot think of a more original name. (But the name

Re: [Development] Feature Freeze Exception: QStringView

2017-02-02 Thread Kevin Kofler
> On Tuesday 31 January 2017 15:24:18 Philippe wrote: >> I just want to highlight, that QStringView is not COW friendly. AFAIK. That alone makes it actually a pessimization. Marc Mutz wrote: > Q6String will likely have the small-string optimisation, so short strings > aren't actually COWed, but d

Re: [Development] Feature Freeze Exception: QStringView

2017-02-02 Thread Kevin Kofler
Alexander Volkov wrote: > Currently it reads into QString as in a buffer and if you need to copy > the buffer, then you > have to manually make a deep copy of it: > QTextStream ts(...); > QString line; > line.reserve(1024); > QStringList found; > while (ts.readLineInto(&lin

Re: [Development] Request moving project to playground area

2017-02-02 Thread Milian Wolff
On Donnerstag, 2. Februar 2017 20:38:00 CET Hamed Masafi wrote: > Project Name: Nut (currently renamed to ORM) > > Description: ORM is a project aimed to help users working with databases. > Developer will write his/her own classes and ORM will generates database > schema and corresponding tables.

[Development] Request moving project to playground area

2017-02-02 Thread Hamed Masafi
Project Name: Nut (currently renamed to ORM) Description: ORM is a project aimed to help users working with databases. Developer will write his/her own classes and ORM will generates database schema and corresponding tables. ORM can generate database migration code (create, drop and alter table an

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

2017-02-02 Thread André Pönitz
On Thu, Feb 02, 2017 at 04:12:37PM +0100, Olivier Goffart wrote: > On Montag, 30. Januar 2017 08:32:50 CET Thiago Macieira wrote: > > On segunda-feira, 30 de janeiro de 2017 14:43:22 PST Konstantin Tokarev > wrote: > > > What about Intel? (IIRC they use EDG frontend, aren't they?) > > > > icc on

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

2017-02-02 Thread Thiago Macieira
On quinta-feira, 2 de fevereiro de 2017 16:12:37 PST Olivier Goffart wrote: > On Montag, 30. Januar 2017 08:32:50 CET Thiago Macieira wrote: > > On segunda-feira, 30 de janeiro de 2017 14:43:22 PST Konstantin Tokarev > > wrote: > > > What about Intel? (IIRC they use EDG frontend, aren't they?) > >

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

2017-02-02 Thread Olivier Goffart
On Montag, 30. Januar 2017 08:32:50 CET Thiago Macieira wrote: > On segunda-feira, 30 de janeiro de 2017 14:43:22 PST Konstantin Tokarev wrote: > > What about Intel? (IIRC they use EDG frontend, aren't they?) > > icc on Mac and Windows operates like GCC and Clang. > > I'll check icl.exe on Windo

Re: [Development] Meeting minutes from Qt Release Team meeting 31.1.2017

2017-02-02 Thread Edward Welbourne
Jani Heikkinen reported an action item of the release team meeting: >>> * API review to be started immediately after final downmerge. I replied with (January 31, 2017 6:52 PM): >> Let me know as soon as that down-merge is done. >> Speaking of API review, review of >> https://codereview.qt-proje

Re: [Development] [Releasing] HEADS-UP: Branching from 'dev' to '5.9' completed

2017-02-02 Thread Edward Welbourne
On Thu, Jan 26, 2017 at 05:28:23AM +, Jani Heikkinen wrote: >> We have now soft branched '5.9' from 'dev'. Target is to have final >> downmerge from 'dev' to '5.9' and Qt 5.9 Feature Freeze 1st of >> February. >> >> Please finalize ongoing changes in 'dev' and start using '5.9' for >> new chang