summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDarrell Anderson <humanreadable@yahoo.com>2012-10-21 16:40:18 -0500
committerDarrell Anderson <humanreadable@yahoo.com>2012-10-21 16:40:18 -0500
commit1ba4ed64cb27aff7bf919f290a8e67d223c94647 (patch)
tree528438040ce4ddb8a1e6f682a53c43cc9e816a11
parent00a35c030ef40653ceb5cec9cc2a79df881675a6 (diff)
downloadtdelibs-1ba4ed64cb27aff7bf919f290a8e67d223c94647.tar.gz
tdelibs-1ba4ed64cb27aff7bf919f290a8e67d223c94647.zip
Fix inadvertent tq changes.
-rw-r--r--tdecore/kdemacros.h.in4
1 files changed, 2 insertions, 2 deletions
diff --git a/tdecore/kdemacros.h.in b/tdecore/kdemacros.h.in
index 04ee7f183..9566c386b 100644
--- a/tdecore/kdemacros.h.in
+++ b/tdecore/kdemacros.h.in
@@ -105,11 +105,11 @@
* this is because usually get called by the class which they belong to,
* and one'd assume that a class author doesn't use deprecated methods of his
* own class. The only exception to this are signals which are connected to
- * other signals; they get invoked from tqmoc-generated code. In any case,
+ * other signals; they get invoked from moc-generated code. In any case,
* printing a warning message in either case is not useful.
* For slots, it can make sense (since slots can be invoked directly) but be
* aware that if the slots get triggered by a signal, the will get called from
- * tqmoc code as well and thus the warnings are useless.
+ * moc code as well and thus the warnings are useless.
*
* \par
* Also note that it is not possible to use KDE_DEPRECATED for classes which