summaryrefslogtreecommitdiffstats
path: root/src/corelib/tools/qstring.cpp
diff options
context:
space:
mode:
Diffstat (limited to 'src/corelib/tools/qstring.cpp')
-rw-r--r--src/corelib/tools/qstring.cpp5
1 files changed, 2 insertions, 3 deletions
diff --git a/src/corelib/tools/qstring.cpp b/src/corelib/tools/qstring.cpp
index a0a3a28b96..8d8bda4644 100644
--- a/src/corelib/tools/qstring.cpp
+++ b/src/corelib/tools/qstring.cpp
@@ -7459,9 +7459,8 @@ QString &QString::setRawData(const QChar *unicode, int size)
Many of QString's member functions are overloaded to accept
\c{const char *} instead of QString. This includes the copy
constructor, the assignment operator, the comparison operators,
- and various other functions such as \link QString::insert()
- insert() \endlink, \link QString::replace() replace()\endlink,
- and \link QString::indexOf() indexOf()\endlink. These functions
+ and various other functions such as \l{QString::insert()}{insert()}, \l{QString::replace()}{replace()},
+ and \l{QString::indexOf()}{indexOf()}. These functions
are usually optimized to avoid constructing a QString object for
the \c{const char *} data. For example, assuming \c str is a
QString,