summaryrefslogtreecommitdiffstats
path: root/doc/qtl.doc
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2024-05-23 14:04:45 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2024-05-27 16:08:54 +0900
commit04913ce7a46fd027856e83a96205fdc388742a19 (patch)
treea04a117317c14854a6b91072658ba0eb3ad8b3fc /doc/qtl.doc
parentc11c0f228b65f7471a26513ef8dbde413e75f8fa (diff)
downloadtqt-04913ce7.tar.gz
tqt-04913ce7.zip
Rename ntqobject*.h and qobject*.cpp to tqobject*
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/qtl.doc')
-rw-r--r--doc/qtl.doc2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/qtl.doc b/doc/qtl.doc
index 5fd0722c7..f2cdf744a 100644
--- a/doc/qtl.doc
+++ b/doc/qtl.doc
@@ -68,7 +68,7 @@ use QPtrCollection 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
-QObjects in a QValueList, but using QPtrList directly seems to be the
+TQObjects in a QValueList, 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
checking than a speed-optimized value based container.