summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqvaluevector.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/tqvaluevector.3qt')
-rw-r--r--doc/man/man3/tqvaluevector.3qt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man/man3/tqvaluevector.3qt b/doc/man/man3/tqvaluevector.3qt
index 2e8dba80..fa8ec1dc 100644
--- a/doc/man/man3/tqvaluevector.3qt
+++ b/doc/man/man3/tqvaluevector.3qt
@@ -186,9 +186,9 @@ The TQValueVector class is a value-based template class that provides a dynamic
.PP
TQValueVector is a TQt implementation of an STL-like vector container. It can be used in your application if the standard \fCvector\fR is not available for your target platforms. TQValueVector is part of the TQt Template Library.
.PP
-TQValueVector<T> defines a template instance to create a vector of values that all have the class T. TQValueVector does not store pointers to the members of the vector; it holds a copy of every member. TQValueVector is said to be value based; in contrast, QPtrList and QDict are pointer based.
+TQValueVector<T> defines a template instance to create a vector of values that all have the class T. TQValueVector does not store pointers to the members of the vector; it holds a copy of every member. TQValueVector is said to be value based; in contrast, TQPtrList and QDict are pointer based.
.PP
-TQValueVector contains and manages a collection of objects of type T and provides random access iterators that allow the contained objects to be addressed. TQValueVector owns the contained elements. For more relaxed ownership semantics, see QPtrCollection and friends, which are pointer-based containers.
+TQValueVector contains and manages a collection of objects of type T and provides random access iterators that allow the contained objects to be addressed. TQValueVector owns the contained elements. For more relaxed ownership semantics, see TQPtrCollection and friends, which are pointer-based containers.
.PP
TQValueVector 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.
.PP