diff options
Diffstat (limited to 'doc/html/ntqdeepcopy.html')
| -rw-r--r-- | doc/html/ntqdeepcopy.html | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/doc/html/ntqdeepcopy.html b/doc/html/ntqdeepcopy.html index ac516d089..2e84c58de 100644 --- a/doc/html/ntqdeepcopy.html +++ b/doc/html/ntqdeepcopy.html @@ -58,33 +58,33 @@ data. use and for maximum speed. In the example below, <tt>s1</tt>, <tt>s2</tt>, <tt>s3</tt>, <tt>s4</tt> and <tt>s5</tt> share data. <p> <pre> // all 5 strings share the same data - <a href="ntqstring.html">TQString</a> s1 = "abcd"; - <a href="ntqstring.html">TQString</a> s2 = s1; - <a href="ntqstring.html">TQString</a> s3 = s2; - <a href="ntqstring.html">TQString</a> s4 = s3; - <a href="ntqstring.html">TQString</a> s5 = s2; + <a href="tqstring.html">TQString</a> s1 = "abcd"; + <a href="tqstring.html">TQString</a> s2 = s1; + <a href="tqstring.html">TQString</a> s3 = s2; + <a href="tqstring.html">TQString</a> s4 = s3; + <a href="tqstring.html">TQString</a> s5 = s2; </pre> <p> TQDeepCopy can be used several ways to ensure that an object references unique, unshared data. In the example below, <tt>s1</tt>, <tt>s2</tt> and <tt>s5</tt> share data, while neither <tt>s3</tt> nor <tt>s4</tt> share data. <pre> // s1, s2 and s5 share the same data, neither s3 nor s4 are shared - <a href="ntqstring.html">TQString</a> s1 = "abcd"; - <a href="ntqstring.html">TQString</a> s2 = s1; + <a href="tqstring.html">TQString</a> s1 = "abcd"; + <a href="tqstring.html">TQString</a> s2 = s1; TQDeepCopy<TQString> s3 = s2; // s3 is a <a href="shclass.html#deep-copy">deep copy</a> of s2 - <a href="ntqstring.html">TQString</a> s4 = s3; // s4 is a deep copy of s3 - <a href="ntqstring.html">TQString</a> s5 = s2; + <a href="tqstring.html">TQString</a> s4 = s3; // s4 is a deep copy of s3 + <a href="tqstring.html">TQString</a> s5 = s2; </pre> <p> In the example below, <tt>s1</tt>, <tt>s2</tt> and <tt>s5</tt> share data, and <tt>s3</tt> and <tt>s4</tt> share data. <pre> // s1, s2 and s5 share the same data, s3 and s4 share the same data - <a href="ntqstring.html">TQString</a> s1 = "abcd"; - <a href="ntqstring.html">TQString</a> s2 = s1; - <a href="ntqstring.html">TQString</a> s3 = TQDeepCopy<TQString>( s2 ); // s3 is a deep copy of s2 - <a href="ntqstring.html">TQString</a> s4 = s3; // s4 is a <a href="shclass.html#shallow-copy">shallow copy</a> of s3 - <a href="ntqstring.html">TQString</a> s5 = s2; + <a href="tqstring.html">TQString</a> s1 = "abcd"; + <a href="tqstring.html">TQString</a> s2 = s1; + <a href="tqstring.html">TQString</a> s3 = TQDeepCopy<TQString>( s2 ); // s3 is a deep copy of s2 + <a href="tqstring.html">TQString</a> s4 = s3; // s4 is a <a href="shclass.html#shallow-copy">shallow copy</a> of s3 + <a href="tqstring.html">TQString</a> s5 = s2; </pre> <p> TQDeepCopy can also provide safety in multithreaded applications @@ -96,7 +96,7 @@ get a unique copy of the data, and that any assignments to <tt>global_string</tt ... - void setGlobalString( const <a href="ntqstring.html">TQString</a> &str ) + void setGlobalString( const <a href="tqstring.html">TQString</a> &str ) { global_mutex.<a href="ntqmutex.html#lock">lock</a>(); global_string = str; // global_string is a deep copy of str @@ -108,7 +108,7 @@ get a unique copy of the data, and that any assignments to <tt>global_string</tt void MyThread::run() { global_mutex.<a href="ntqmutex.html#lock">lock</a>(); - <a href="ntqstring.html">TQString</a> str = global_string; // str is a deep copy of global_string + <a href="tqstring.html">TQString</a> str = global_string; // str is a deep copy of global_string global_mutex.<a href="ntqmutex.html#unlock">unlock</a>(); // process the string data @@ -121,7 +121,7 @@ get a unique copy of the data, and that any assignments to <tt>global_string</tt <p> <b>Warning:</b> It is the application developer's responsibility to protect the object shared across multiple threads. -<p> The examples above use <a href="ntqstring.html">TQString</a>, which is an implicitly shared +<p> The examples above use <a href="tqstring.html">TQString</a>, which is an implicitly shared class. The behavior of TQDeepCopy is the same when using explicitly shared classes like <a href="qbytearray.html">TQByteArray</a>. <p> Currently, TQDeepCopy works with the following classes: @@ -129,7 +129,7 @@ shared classes like <a href="qbytearray.html">TQByteArray</a>. <li> <a href="ntqmemarray.html">TQMemArray</a> (including subclasses like TQByteArray and <a href="ntqcstring.html">TQCString</a>) <li> <a href="tqmap.html">TQMap</a> <li> TQString -<li> <a href="tqvaluelist.html">TQValueList</a> (including subclasses like <a href="ntqstringlist.html">TQStringList</a> and <a href="tqvaluestack.html">TQValueStack</a>) +<li> <a href="tqvaluelist.html">TQValueList</a> (including subclasses like <a href="tqstringlist.html">TQStringList</a> and <a href="tqvaluestack.html">TQValueStack</a>) <li> <a href="tqvaluevector.html">TQValueVector</a> </ul> <p> <p>See also <a href="threads.html">Thread Support in TQt</a>, <a href="shared.html">Implicitly and Explicitly Shared Classes</a>, and <a href="tools.html">Non-GUI Classes</a>. |