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.3qt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man/man3/tqvaluevector.3qt b/doc/man/man3/tqvaluevector.3qt
index c2e9caef..2c382739 100644
--- a/doc/man/man3/tqvaluevector.3qt
+++ b/doc/man/man3/tqvaluevector.3qt
@@ -395,7 +395,7 @@ By creating a TQValueVector with a sufficiently large initial size, there will b
.PP
Because TQValueVector 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().
.PP
-TQValueVector is shared implicitly, which means it can be copied in constant time. If multiple TQValueVector 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 TQValueVector is being used in a multi-threaded program, you must protect all access to the vector. See QMutex.
+TQValueVector is shared implicitly, which means it can be copied in constant time. If multiple TQValueVector 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 TQValueVector is being used in a multi-threaded program, you must protect all access to the vector. See TQMutex.
.PP
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.
.PP