diff options
Diffstat (limited to 'doc/qtl.doc')
| -rw-r--r-- | doc/qtl.doc | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/qtl.doc b/doc/qtl.doc index 2c3ab4e34..173bd6fdd 100644 --- a/doc/qtl.doc +++ b/doc/qtl.doc @@ -64,13 +64,13 @@ differences, but is often a little slower and often expands to less object code. If you cannot make copies of the objects you want to store you should -use QPtrCollection and friends, all of which operate on pointers +use TQPtrCollection and friends, all of which operate on pointers rather than values. This applies, for example, to all classes derived from \l TQObject. A TQObject does not have a copy constructor, so using it as value is impossible. You may choose to store pointers to -TQObjects in a TQValueList, but using QPtrList directly seems to be the -better choice for this kind of application domain. QPtrList, like all -other QPtrCollection based containers, provides far more sanity +TQObjects in a TQValueList, but using TQPtrList 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. If you have objects that implement value semantics, and the STL is not @@ -94,7 +94,7 @@ TQString and all simple C++ types, such as int, bool or double. The TQt Template Library is designed for speed. Iterators are extremely fast. To achieve this performance, less error checking is done than in -the QPtrCollection based containers. A QTL container, for example, +the TQPtrCollection based containers. A QTL 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. |