summaryrefslogtreecommitdiffstats
path: root/doc/src/development/debug.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/development/debug.qdoc')
-rw-r--r--doc/src/development/debug.qdoc8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/development/debug.qdoc b/doc/src/development/debug.qdoc
index 653e8629a..a94af25b0 100644
--- a/doc/src/development/debug.qdoc
+++ b/doc/src/development/debug.qdoc
@@ -138,7 +138,7 @@
If you include the <QtDebug> header file, the \c qDebug() function
can also be used as an output stream. For example:
- \snippet doc/src/snippets/code/doc_src_debug.cpp 0
+ \snippet snippets/code/doc_src_debug.cpp 0
The Qt implementation of these functions prints to the
\c stderr output under Unix/X11 and Mac OS X. With Windows, if it
@@ -189,7 +189,7 @@
between each item. Here is an example for a class that represents
a 2D coordinate.
- \snippet doc/src/snippets/qdebug/qdebugsnippet.cpp 0
+ \snippet snippets/qdebug/qdebugsnippet.cpp 0
Integration of custom types with Qt's meta-object system is covered
in more depth in the \l{Creating Custom Qt Types} document.
@@ -215,14 +215,14 @@
These macros are useful for detecting program errors, e.g. like this:
- \snippet doc/src/snippets/code/doc_src_debug.cpp 1
+ \snippet snippets/code/doc_src_debug.cpp 1
Q_ASSERT(), Q_ASSERT_X(), and Q_CHECK_PTR() expand to nothing if
\c QT_NO_DEBUG is defined during compilation. For this reason,
the arguments to these macro should not have any side-effects.
Here is an incorrect usage of Q_CHECK_PTR():
- \snippet doc/src/snippets/code/doc_src_debug.cpp 2
+ \snippet snippets/code/doc_src_debug.cpp 2
If this code is compiled with \c QT_NO_DEBUG defined, the code in
the Q_CHECK_PTR() expression is not executed and \e alloc returns