From e6077c30d14e9d662e8843c554db86c0d366d0b6 Mon Sep 17 00:00:00 2001 From: Michele Calgaro Date: Thu, 6 Jun 2024 13:44:12 +0900 Subject: Rename str nt* related files to equivalent tq* Signed-off-by: Michele Calgaro --- doc/man/man3/tqcstring.3qt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/man/man3/tqcstring.3qt') diff --git a/doc/man/man3/tqcstring.3qt b/doc/man/man3/tqcstring.3qt index 60802a2d0..151345889 100644 --- a/doc/man/man3/tqcstring.3qt +++ b/doc/man/man3/tqcstring.3qt @@ -328,7 +328,7 @@ Many operators are overloaded to work with QCStrings. QCString also supports som .PP In QCString the notion of uppercase and lowercase and of which character is greater than or less than another character is locale dependent. This affects functions which support a case insensitive option or which compare or lowercase or uppercase their arguments. Case insensitive operations and comparisons will be accurate if both strings contain only ASCII characters. (If \fC$LC_CTYPE\fR is set, most Unix systems do "the right thing".) Functions that this affects include contains(), find(), findRev(), operator<(), operator<=(), operator>(), operator>=(), lower() and upper(). .PP -This issue does not apply to QStrings since they represent characters using Unicode. +This issue does not apply to TQStrings since they represent characters using Unicode. .PP Performance note: The QCString methods for QRegExp searching are implemented by converting the QCString to a TQString and performing the search on that. This implies a deep copy of the QCString data. If you are going to perform many QRegExp searches on a large QCString, you will get better performance by converting the QCString to a TQString yourself, and then searching in the TQString. .PP -- cgit v1.2.3