[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-freeqt
Subject:    Re: [freeqt] STL or Qt containers?
From:       Stephan Kulow <coolo () itm ! mu-luebeck ! de>
Date:       1998-11-14 20:37:21
[Download RAW message or body]

> 
> *-Lokh <Patrice.Fortier@aquarel.fr>
> |
> |   I'm about to write the functions qwidget::find(), qapplication::allWidgets()
> | and qapplication::topLevelWidgets().
> | As we don't have any  X window to qwidget function (in fact this is done
> | by find()), and I don't know if this is usefull to store such data for
> | all the widgets, I plan to store a list of the toplevel widgets of the
> | application (in qapplication for ex.) and use recursive search functions.
> | 
> | My problem is the following one:
> | Should I use an STL list or a Qt list? Considering that topLevelWidget()
> | and allWidgets() return a QWidgetList, I'd go for the latter but...
> 
> The STL is so much better than the Qt containers. I seem to remember
> having heard that Qt will use STL in the future.
This is very unlikely to happen since qt aims to be as platform independent
as possible and STL is as non-standard as a standard can be :)
> 
> Are QList and friends needed often as arguments or return values? If
> not, I would use STL internally and convert to Qt containers when needed.
I would say use always QList if speed is not an issue.

Greetings, Stephan

-- 
Stephan Kulow (coolo@kde.org)
detrever lleps ot ysae ylgnizama s'ti

[prev in list] [next in list] [prev in thread] [next in thread]