summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqdeepcopy.3qt
diff options
context:
space:
mode:
authorMichele Calgaro <[email protected]>2023-09-23 12:42:20 +0900
committerMichele Calgaro <[email protected]>2023-09-23 12:42:20 +0900
commitb35e0845dc9b3c8b9a5e52a682c769f383933fae (patch)
treee4eeca8f6fe0ca87e774be98eabf89b4c7fca347 /doc/man/man3/tqdeepcopy.3qt
parent1ba13366a7a377d50b9e8df9044ce11d8209f98c (diff)
downloadtqt3-b35e0845dc9b3c8b9a5e52a682c769f383933fae.tar.gz
tqt3-b35e0845dc9b3c8b9a5e52a682c769f383933fae.zip
Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* version
Signed-off-by: Michele Calgaro <[email protected]>
Diffstat (limited to 'doc/man/man3/tqdeepcopy.3qt')
-rw-r--r--doc/man/man3/tqdeepcopy.3qt40
1 files changed, 20 insertions, 20 deletions
diff --git a/doc/man/man3/tqdeepcopy.3qt b/doc/man/man3/tqdeepcopy.3qt
index 7c906b55a..6275ab594 100644
--- a/doc/man/man3/tqdeepcopy.3qt
+++ b/doc/man/man3/tqdeepcopy.3qt
@@ -37,15 +37,15 @@ Normally, shared copies reference the same data to optimize memory use and for m
.br
// all 5 strings share the same data
.br
- QString s1 = "abcd";
+ TQString s1 = "abcd";
.br
- QString s2 = s1;
+ TQString s2 = s1;
.br
- QString s3 = s2;
+ TQString s3 = s2;
.br
- QString s4 = s3;
+ TQString s4 = s3;
.br
- QString s5 = s2;
+ TQString s5 = s2;
.br
.fi
.PP
@@ -55,15 +55,15 @@ QDeepCopy can be used several ways to ensure that an object references unique, u
.br
// s1, s2 and s5 share the same data, neither s3 nor s4 are shared
.br
- QString s1 = "abcd";
+ TQString s1 = "abcd";
.br
- QString s2 = s1;
+ TQString s2 = s1;
.br
- QDeepCopy<QString> s3 = s2; // s3 is a deep copy of s2
+ QDeepCopy<TQString> s3 = s2; // s3 is a deep copy of s2
.br
- QString s4 = s3; // s4 is a deep copy of s3
+ TQString s4 = s3; // s4 is a deep copy of s3
.br
- QString s5 = s2;
+ TQString s5 = s2;
.br
.fi
.PP
@@ -73,15 +73,15 @@ In the example below, \fCs1\fR, \fCs2\fR and \fCs5\fR share data, and \fCs3\fR a
.br
// s1, s2 and s5 share the same data, s3 and s4 share the same data
.br
- QString s1 = "abcd";
+ TQString s1 = "abcd";
.br
- QString s2 = s1;
+ TQString s2 = s1;
.br
- QString s3 = QDeepCopy<QString>( s2 ); // s3 is a deep copy of s2
+ TQString s3 = QDeepCopy<TQString>( s2 ); // s3 is a deep copy of s2
.br
- QString s4 = s3; // s4 is a shallow copy of s3
+ TQString s4 = s3; // s4 is a shallow copy of s3
.br
- QString s5 = s2;
+ TQString s5 = s2;
.br
.fi
.PP
@@ -89,7 +89,7 @@ QDeepCopy can also provide safety in multithreaded applications that use shared
.PP
.nf
.br
- QDeepCopy<QString> global_string; // global string data
+ QDeepCopy<TQString> global_string; // global string data
.br
QMutex global_mutex; // mutex to protext global_string
.br
@@ -97,7 +97,7 @@ QDeepCopy can also provide safety in multithreaded applications that use shared
...
.br
.br
- void setGlobalString( const QString &str )
+ void setGlobalString( const TQString &str )
.br
{
.br
@@ -119,7 +119,7 @@ QDeepCopy can also provide safety in multithreaded applications that use shared
.br
global_mutex.lock();
.br
- QString str = global_string; // str is a deep copy of global_string
+ TQString str = global_string; // str is a deep copy of global_string
.br
global_mutex.unlock();
.br
@@ -139,7 +139,7 @@ QDeepCopy can also provide safety in multithreaded applications that use shared
.PP
\fBWarning:\fR It is the application developer's responsibility to protect the object shared across multiple threads.
.PP
-The examples above use QString, which is an implicitly shared class. The behavior of QDeepCopy is the same when using explicitly shared classes like QByteArray.
+The examples above use TQString, which is an implicitly shared class. The behavior of QDeepCopy is the same when using explicitly shared classes like QByteArray.
.PP
Currently, QDeepCopy works with the following classes:
.TP
@@ -147,7 +147,7 @@ QMemArray (including subclasses like QByteArray and QCString)
.TP
QMap
.TP
-QString
+TQString
.TP
QValueList (including subclasses like QStringList and QValueStack)
.TP