This rather nicely proves my point. Jason isn't even new to this list and he didn't realize the problems. No, community as a whole did _not _ have "years and years" to port away from QList
On Mon, May 20, 2019 at 6:07 PM Jean-Michaël Celerier < jeanmichael.celer...@gmail.com> wrote: > > QList is just a linked list > > you're in for a rude awakening :-) https://doc.qt.io/qt-5/qlist.html > > On Mon, May 20, 2019 at 5:03 PM Jason H <jh...@gmx.com> wrote: > >> >> > Ok, QList as an alias for QVector takes care of the technical issues I >> > have with using inheritance. It doesn't address my concerns regarding >> > breaking QList behaviour. What purpose is served to call something QList >> > that is in fact a QVector? Please spell it out for me, as I don't see >> > it. >> >> My understanding is that QVector requires contiguous memory, consuming a >> giant block for all the items in the list. QList is just a linked list. >> QVector will fail sooner when memory fragmentation is a problem. I would >> expect systems with long-running processes and limited RAM (i.e. embedded, >> a Raspberry Pi, phone, etc) to encounter this sooner than other systems, >> especially when the size of each object is large. (You could always just >> store pointers though) >> >> >> _______________________________________________ >> Development mailing list >> Development@qt-project.org >> https://lists.qt-project.org/listinfo/development >> > _______________________________________________ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development >
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
