Viadeo Twitter Google Bookmarks ! Facebook Digg del.icio.us MySpace Yahoo MyWeb Blinklist Netvouz Reddit Simpy StumbleUpon Bookmarks Windows Live Favorites 
Logo Documentation Qt ·  Page d'accueil  ·  Tous les espaces de nom  ·  Toutes les classes  ·  Classes principales  ·  Annotées  ·  Classes groupées  ·  Modules  ·  Fonctions  · 

Q3ValueVector Class Reference
[Qt3Support module]

The Q3ValueVector class is a value-based template class that provides a dynamic array. More...

 #include <Q3ValueVector>

This class is part of the Qt 3 support library. It is provided to keep old source code working. We strongly advise against using it in new code. See Porting to Qt 4 for more information.

Inherits QVector<T>.

Public Functions

  • Q3ValueVector ( const Q3ValueVector<T> & v )
  • Q3ValueVector ( QVector<T>::size_type n, const T & val = T() )
  • Q3ValueVector ( const std::vector<T> & v )
  • T & at ( int i, bool * ok = 0 )
  • const T & at ( int i, bool * ok = 0 ) const
  • void resize ( int n, const T & val = T() )
  • Q3ValueVector<T> & operator= ( const Q3ValueVector<T> & v )
  • Q3ValueVector<T> & operator= ( const std::vector<T> & v )
  • 62 public functions inherited from QVector

Additional Inherited Members

  • 2 static public members inherited from QVector

Detailed Description

The Q3ValueVector class is a value-based template class that provides a dynamic array.

Q3ValueVector is a Qt implementation of an STL-like vector container. It can be used in your application if the standard vector is not available for your target platforms.

Q3ValueVector<T> defines a template instance to create a vector of values that all have the class T. Q3ValueVector does not store pointers to the members of the vector; it holds a copy of every member. Q3ValueVector is said to be value based; in contrast, Q3PtrList and Q3Dict are pointer based.

Q3ValueVector contains and manages a collection of objects of type T and provides random access iterators that allow the contained objects to be addressed. Q3ValueVector owns the contained elements. For more relaxed ownership semantics, see Q3PtrCollection and friends, which are pointer-based containers.

Q3ValueVector provides good performance if you append or remove elements from the end of the vector. If you insert or remove elements from anywhere but the end, performance is very bad. The reason for this is that elements must to be copied into new positions.

Some classes cannot be used within a Q3ValueVector: for example, all classes derived from QObject and thus all classes that implement widgets. Only values can be used in a Q3ValueVector. To qualify as a value the class must provide:

  • a copy constructor;
  • an assignment operator;
  • a default constructor, i.e., a constructor that does not take any arguments.

Note that C++ defaults to field-by-field assignment operators and copy constructors if no explicit version is supplied. In many cases this is sufficient.

Q3ValueVector uses an STL-like syntax to manipulate and address the objects it contains.

Example:

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

 class Employee
 {
 public:
     Employee(): s(0) {}
     Employee( const QString& name, int salary )
         : n( name ), s( salary )
     { }

     QString name()   const          { return n; }
     int     salary() const          { return s; }
     void    setSalary( int salary ) { s = salary; }
 private:
     QString n;
     int     s;
 };

 int main()
 {
     typedef Q3ValueVector<Employee> EmployeeVector;
     EmployeeVector vec( 3 );  // vector of 3 Employees

     vec[0] = Employee( "Bill", 50000 );
     vec[1] = Employee( "Steve", 80000 );
     vec[2] = Employee( "Ron", 60000 );

     Employee joe( "Joe", 50000 );
     vec.push_back( joe );  // vector expands to accommodate 4 Employees
     joe.setSalary( 70000 );

     EmployeeVector::iterator it;
     for( it = vec.begin(); it != vec.end(); ++it )
         printf( "%s earns %d\n", (*it).name().latin1(), (*it).salary() );

     return 0;
 }

Program output:

     Bill earns 50000
     Steve earns 80000
     Ron earns 60000
     Joe earns 50000

As you can see, the most recent change to Joe's salary did not affect the value in the vector because the vector created a copy of Joe's entry.

Many Qt functions return const value vectors; to iterate over these you should make a copy and iterate over the copy.

There are several ways to find items in the vector. The begin() and end() functions return iterators to the beginning and end of the vector. The advantage of getting an iterator is that you can move forward or backward from this position by incrementing/decrementing the iterator. The iterator returned by end() points to the element which is one past the last element in the container. The past-the-end iterator is still associated with the vector it belongs to, however it is not dereferenceable; operator*() will not return a well-defined value. If the vector is empty(), the iterator returned by begin() will equal the iterator returned by end().

The fastest way to access an element of a vector is by using operator[]. This function provides random access and will return a reference to the element located at the specified index. Thus, you can access every element directly, in constant time, providing you know the location of the element. It is undefined to access an element that does not exist (your application will probably crash). For example:

 Q3ValueVector<int> vec1;  // an empty vector
 vec1[10] = 4;  // WARNING: undefined, probably a crash

 Q3ValueVector<QString> vec2(25); // initialize with 25 elements
 vec2[10] = "Dave";  // OK

Whenever inserting, removing or referencing elements in a vector, always make sure you are referring to valid positions. For example:

 void func( Q3ValueVector<int>& vec )
 {
     if ( vec.size() > 10 ) {
         vec[9] = 99; // OK
     }
 };

The iterators provided by vector are random access iterators, therefore you can use them with many generic algorithms, for example, algorithms provided by the STL.

It is safe to have multiple iterators on the vector at the same time. Since Q3ValueVector manages memory dynamically, all iterators can become invalid if a memory reallocation occurs. For example, if some member of the vector is removed, iterators that point to the removed element and to all following elements become invalidated. Inserting into the middle of the vector will invalidate all iterators. For convenience, the function back() returns a reference to the last element in the vector, and front() returns a reference to the first element. If the vector is empty(), both back() and front() have undefined behavior (your application will crash or do unpredictable things). Use back() and front() with caution, for example:

 Q3ValueVector<int> vec( 3 );
 vec.push_back( 1 );
 vec.push_back( 2 );
 vec.push_back( 3 );
 ...
 if ( !vec.empty() ) {
     // OK: modify the first element
     int& i = vec.front();
     i = 18;
 }
 ...
 Q3ValueVector<double> dvec;
 double d = dvec.back(); // undefined behavior

Because Q3ValueVector manages memory dynamically, it is recommended that you contruct a vector with an initial size. Inserting and removing elements happens fastest when:

  • Inserting or removing elements happens at the end() of the vector;
  • The vector does not need to allocate additional memory.

By creating a Q3ValueVector with a sufficiently large initial size, there will be less memory allocations. Do not use an initial size that is too big, since it will still take time to construct all the empty entries, and the extra space will be wasted if it is never used.

Because Q3ValueVector is value-based there is no need to be careful about deleting elements in the vector. The vector holds its own copies and will free them if the corresponding member or the vector itself is deleted. You can force the vector to free all of its items with clear().

Q3ValueVector is shared implicitly, which means it can be copied in constant time. If multiple Q3ValueVector instances share the same data and one needs to modify its contents, this modifying instance makes a copy and modifies its private copy; it thus does not affect the other instances. This is often called "copy on write". If a Q3ValueVector is being used in a multi-threaded program, you must protect all access to the vector. See QMutex.

There are several ways to insert elements into the vector. The push_back() function insert elements into the end of the vector, and is usually fastest. The insert() function can be used to add elements at specific positions within the vector.

Items can be also be removed from the vector in several ways. There are several variants of the erase() function which removes a specific element, or range of elements, from the vector.

Q3ValueVector stores its elements in contiguous memory. This means that you can use a Q3ValueVector in any situation that requires an array.


Member Function Documentation

Q3ValueVector::Q3ValueVector ()

Constructs an empty vector without any elements. To create a vector which reserves an initial amount of space for elements, use Q3ValueVector(size_type n).

Q3ValueVector::Q3ValueVector ( const Q3ValueVector<T> & v )

Constructs a copy of v.

This operation costs O(1) time because Q3ValueVector is implicitly shared.

The first modification to the vector does takes O(n) time, because the elements must be copied.

Q3ValueVector::Q3ValueVector ( QVector<T>::size_type n, const T & val = T() )

Constructs a vector with an initial size of n elements. Each element is initialized with the value of val.

Q3ValueVector::Q3ValueVector ( const std::vector<T> & v )

This operation costs O(n) time because v is copied.

T & Q3ValueVector::at ( int i, bool * ok = 0 )

Returns a reference to the element with index i. If ok is non-null, and the index i is out of range, *ok is set to FALSE and the returned reference is undefined. If the index i is within the range of the vector, and ok is non-null, *ok is set to TRUE and the returned reference is well defined.

const T & Q3ValueVector::at ( int i, bool * ok = 0 ) const

This is an overloaded member function, provided for convenience.

Returns a const reference to the element with index i. If ok is non-null, and the index i is out of range, *ok is set to FALSE and the returned reference is undefined. If the index i is within the range of the vector, and ok is non-null, *ok is set to TRUE and the returned reference is well defined.

void Q3ValueVector::resize ( int n, const T & val = T() )

Changes the size of the vector to n. If n is greater than the current size(), elements are added to the end and initialized with the value of val. If n is less than size(), elements are removed from the end. If n is equal to size() nothing happens.

Q3ValueVector<T> & Q3ValueVector::operator= ( const Q3ValueVector<T> & v )

Assigns v to this vector and returns a reference to this vector.

All iterators of the current vector become invalidated by this operation. The cost of such an assignment is O(1) since Q3ValueVector is implicitly shared.

Q3ValueVector<T> & Q3ValueVector::operator= ( const std::vector<T> & v )

This is an overloaded member function, provided for convenience.

Assigns v to this vector and returns a reference to this vector.

All iterators of the current vector become invalidated by this operation. The cost of this assignment is O(n) since v is copied.

Publicité

Best Of

Actualités les plus lues

Semaine
Mois
Année
  1. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 85
  2. Apercevoir la troisième dimension ou l'utilisation multithreadée d'OpenGL dans Qt, un article des Qt Quarterly traduit par Guillaume Belz 0
  3. Les développeurs ignorent-ils trop les failles découvertes dans leur code ? Prenez-vous en compte les remarques des autres ? 17
  4. BlackBerry 10 : premières images du prochain OS de RIM qui devrait intégrer des widgets et des tuiles inspirées de Windows Phone 0
  5. Pourquoi les programmeurs sont-ils moins payés que les gestionnaires de programmes ? Manquent-ils de pouvoir de négociation ? 19
  6. Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
  7. Adieu qmake, bienvenue qbs : Qt Building Suite, un outil déclaratif et extensible pour la compilation de projets Qt 17
Page suivante

Le Qt Quarterly au hasard

Logo

Requête de données génériques avec QtXmlPatterns et XQuery

Qt Quarterly est la revue trimestrielle proposée par Nokia et à destination des développeurs Qt. Ces articles d'une grande qualité technique sont rédigés par des experts Qt. Lire l'article.

Communauté

Ressources

Liens utiles

Contact

  • Vous souhaitez rejoindre la rédaction ou proposer un tutoriel, une traduction, une question... ? Postez dans le forum Contribuez ou contactez-nous par MP ou par email (voir en bas de page).

Qt dans le magazine

Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. Qt 4.3
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD.
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP !
 
 
 
 
Partenaires

Hébergement Web