HomeHome

Collection Classes


A collection class is a class that can contain a number of items in a certain data structure and perform operations on the contained items; insert, remove, find etc.

Qt has many reference based collection classes and some value based collections.

The reference based collections are:

The value based collections are:

The reference based collection classes work with pointers to items, while the value based classes store copies of their items. An exception is QArray. It is neither reference nor value based, but memory based. For maximum efficiency with the simple data types usually used in arrays, it uses bitwise operations to copy and compare array elements.

Some of these classes have corresponding iterators. An iterator is a class for traversing the items in a collection:

The value based collections plus algorithms operating on them are grouped together in the Qt Template Library. See the respective documentation for details. The rest of this page talks about the reference based containers only.

Architecture of the reference based containers

There are three internal base classes for the reference based containers; QGCache, QGDict and QGList that operate on void* pointers. A thin template layer implements the actual collections by casting item pointers to and from void*.

This strategy allows Qt's templates to be very economical on space (instantiating one of these templates adds only inline-able calls to the base classes), while it does not hurt performance too much.

A QList Example

This example shows how to store Employee items in a list and prints them out in the reverse order:

    #include <qlist.h>
    #include <qstring.h>
    #include <stdio.h>

    class Employee
    {
    public:
        Employee( const char *name, int salary ) { n=name; s=salary; }
        const char *name()   const               { return n; }
        int         salary() const               { return s; }
    private:
        QString     n;
        int         s;
    };

    void main()
    {
        QList<Employee> list;           // list of pointers to Employee
        list.setAutoDelete( TRUE );     // delete items when they are removed

        list.append( new Employee("Bill", 50000) );
        list.append( new Employee("Steve",80000) );
        list.append( new Employee("Ron",  60000) );

        QListIterator<Employee> it(list); // iterator for employee list
        for ( it.toLast(); it.current(); --it) ) {
            Employee *emp = it.current();
            printf( "%s earns %d\n", emp->name(), emp->salary() );
        }
    }

Program output:

        Ron earns 60000
        Steve earns 80000
        Bill earns 50000

Managing Collection Items

All reference based collections inherit the QCollection base class. This class knows only the number of items in the collection and the delete strategy.

Items in a collection are by default not deleted when they are removed from the collection. The QCollection::setAutoDelete() function specifies the delete strategy. In the list example, we enable auto-deletion to make the list delete the items when they are removed from the list.

When inserting an item into a collection, only the pointer is copied, not the item itself. This is called a shallow copy. It is possible to make the collection copy all of the item's data (known as a deep copy) when an item is inserted. All collection functions that insert an item call the virtual function QCollection::newItem() for the item to be inserted. Inherit a collection and reimplement it if you want to have deep copies in your collection.

When removing an item from a list, the virtual function QCollection::deleteItem() is called. The default implementation in all collection classes deletes the item if auto-deletion is enabled.

Usage

A reference based collection class, such as QList<type>, defines a collection of pointers to type objects. The pointer (*) is implicit.

We discuss QList here, but the same techniques apply for all reference based collection classes and all collection class iterators.

Template instantiation:

  QList<Employee> list;         // wherever the list is used

The item's class or type, Employee in our example, must be defined prior to the list definition.

  // Does not work: Employee is not defined
  class Employee;
  QList<Employee> list;

  // This works: Employee is defined before it is used
  class Employee {
    ...
  };
  QList<Employee> list;

Iterators

Although QList has member functions to traverse the list, it can often be better to make use of an iterator. QListIterator is very safe and can traverse lists that are being modified at the same time. Multiple iterators can work independently on the same collection.

A QList has an internal list of all iterators that are currently operating on the list. When a list entry is removed, the list updates all iterators to point to this entry.

The QDict and QCache collections have no traversal functions. To traverse these collections, you must use QDictIterator or QCacheIterator.

Predefined Collections

Qt has the following predefined collection classes:

In almost all cases you would choose QStringList, which is a value list of implicitly shared QString unicode strings. QStrList and QStrIList only store char* pointers.

Comparison with the STL

We often get questions about why Qt does not use the STL, and why Qt's container templates are provided at all. Here are the major factors why we use and provide these templates:

Value based containers in the style of the STL do have one major advantage, though: They are extremely efficient when being used with value objects that implement a fast copy constructor. This is the case with all implicit shared Qt classes such as QString or any of the C++ standard data types like int, bool or double. Since we needed that functionality for Qt itself, we added a few value based containers in Qt-2.0. As with the other containers, the new ones have a well documented interface and a naming scheme that matches the usual Qt conventions - another advantage over the STL classes.

There are other differences, but the ones above are the important reasons behind our decision to write, use and provide these classes.

Classes:


Copyright © 2005 TrolltechTrademarks
Qt version 2.3.10