Re: [Development] Qt LTS & C++11 plans (CopperSpice)

2015-07-26 Thread André Somers
Op 27-7-2015 om 03:47 schreef Ansel Sermersheim: > On 7/26/15 3:01 PM, Kevin Kofler wrote: >> Ansel Sermersheim wrote: >>> We do in fact have a CLA in place. However, our CLA has one single >>> purpose. In the event that Qt is re-licensed under a BSD style license >>> (whether due to the KDE Free Q

Re: [Development] HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

2015-07-26 Thread Giuseppe D'Angelo
On Mon, Jul 27, 2015 at 12:27 AM, Kevin Kofler wrote: > > It doesn't switch the stuff it actually guarantees: > * Moving n elements in the list (for whatever reason) will only move > n*sizeof(void*) bytes (not n*sizeof(T), nor will it call any copy > constructors or destructors). True, althou

Re: [Development] Qt LTS & C++11 plans (CopperSpice)

2015-07-26 Thread Ansel Sermersheim
On 7/26/15 3:01 PM, Kevin Kofler wrote: > Ansel Sermersheim wrote: >> We do in fact have a CLA in place. However, our CLA has one single >> purpose. In the event that Qt is re-licensed under a BSD style license >> (whether due to the KDE Free Qt Foundation or some other reason), we >> will re-licen

Re: [Development] HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

2015-07-26 Thread Thiago Macieira
On Monday 27 July 2015 00:19:16 Kevin Kofler wrote: > Thiago Macieira wrote: > > Except if the type is larger than sizeof(void*), like QVariant is. > > > > Or like QString and QByteArray will be in Qt 6. > > Ewww, are you sure that that's a good idea? Yes. -- Thiago Macieira - thiago.macieira (

Re: [Development] HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

2015-07-26 Thread Kevin Kofler
PS: Oops: I wrote: > * Inserting an element performs at most 1 heap allocation. Before the hair-splitting begins, at most amortized 1, worst-case 2. Kevin Kofler ___ Development mailing list Development@qt-project.org http://lists.qt-project.o

Re: [Development] HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

2015-07-26 Thread Kevin Kofler
Marc Mutz wrote: > It makes perfect sense: A container should not subtle change memory layout > and switch guarantees in such a way that only experts know what it > actually does. That an array-list *might* be the most efficient container > for certain types and certain operations, no-one disputes.

[Development] Backwards compatibiltiy break in Qt 5.5

2015-07-26 Thread NIkolai Marchenko
(I am not entirely sure why I haven't received at least a notification of why this post has not appeared the first time I tried to send it, so here we go again. Btw, it was Thiago Macieira himself who actually suggested I mail this list) Hi! We (Russian Qt community) have a situation we could not

Re: [Development] HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

2015-07-26 Thread Kevin Kofler
Thiago Macieira wrote: > Except if the type is larger than sizeof(void*), like QVariant is. > > Or like QString and QByteArray will be in Qt 6. Ewww, are you sure that that's a good idea? Kevin Kofler ___ Development mailing list Development@q

Re: [Development] Qt LTS & C++11 plans (CopperSpice)

2015-07-26 Thread Kevin Kofler
Ansel Sermersheim wrote: > We do in fact have a CLA in place. However, our CLA has one single > purpose. In the event that Qt is re-licensed under a BSD style license > (whether due to the KDE Free Qt Foundation or some other reason), we > will re-license CopperSpice under that same license. That i