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

[Smith Martin]

>Can we please avoid turning this thread into "why is QList" bad?

Sorry, you're the one who said it's bad; I'm quite happy with it. I'm asking if QList<C> becomes QList<C*> even if I declare it as QList<C>.

martin

________________________________________
From: development-bounces+martin.smith=theqtcompany.com at qt-project.org <development-bounces+martin.smith=theqtcompany.com at qt-project.org> on behalf of Marc Mutz <marc.mutz at kdab.com>
Sent: Friday, July 10, 2015 1:25 PM
To: development at qt-project.org
Subject: Re: [Development] HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

On Friday 10 July 2015 11:54:16 Smith Martin wrote:
> Then I don't see why it is so inherently inefficient. The QList entry is
> allocated on the heap anyway. Doesn't QList<C> just allocate a bigger
> entry? And if I don't have the C object stored anywhere else, it has to be
> somewhere, so why not keep it in the QList entry?

Can we please avoid turning this thread into "why is QList" bad?

QList *is* bad. If you don't believe, read
http://marcmutz.wordpress.com/effective-qt/ If you then _still_ don't believe,
do your own benchmarks. Then you will believe.

Thanks,
Marc

--
Marc Mutz <marc.mutz at kdab.com> | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development