summaryrefslogtreecommitdiffstats
path: root/doc/html/qt-template-lib.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/qt-template-lib.html')
-rw-r--r--doc/html/qt-template-lib.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/html/qt-template-lib.html b/doc/html/qt-template-lib.html
index 296778444..a96e9b7f0 100644
--- a/doc/html/qt-template-lib.html
+++ b/doc/html/qt-template-lib.html
@@ -51,11 +51,11 @@ of the STL container API. Compared with the STL, TQTL has no platform
differences, but is often a little slower and often expands to less
object code.
<p> If you cannot make copies of the objects you want to store you should
-use <a href="ntqptrcollection.html">TQPtrCollection</a> and friends, all of which operate on pointers
+use <a href="tqptrcollection.html">TQPtrCollection</a> and friends, all of which operate on pointers
rather than values. This applies, for example, to all classes derived
from <a href="tqobject.html">TQObject</a>. A <a href="tqobject.html">TQObject</a> does not have a copy constructor, so using
it as value is impossible. You may choose to store pointers to
-TQObjects in a <a href="tqvaluelist.html">TQValueList</a>, but using <a href="ntqptrlist.html">TQPtrList</a> directly seems to be the
+TQObjects in a <a href="tqvaluelist.html">TQValueList</a>, but using <a href="tqptrlist.html">TQPtrList</a> directly seems to be the
better choice for this kind of application domain. TQPtrList, like all
other TQPtrCollection based containers, provides far more sanity
checking than a speed-optimized value based container.
@@ -76,7 +76,7 @@ your data's class.
<a href="ntqstring.html">TQString</a> and all simple C++ types, such as int, bool or double.
<p> The TQt Template Library is designed for speed. Iterators are extremely
fast. To achieve this performance, less error checking is done than in
-the <a href="ntqptrcollection.html">TQPtrCollection</a> based containers. A TQTL container, for example,
+the <a href="tqptrcollection.html">TQPtrCollection</a> based containers. A TQTL container, for example,
does not track any associated iterators. This makes certain validity
checks, for example when removing items, impossible to perform
automatically, but does lead to extremely good performance.