summaryrefslogtreecommitdiffstats
path: root/kdecore/kdemacros.h.in
diff options
context:
space:
mode:
Diffstat (limited to 'kdecore/kdemacros.h.in')
-rw-r--r--kdecore/kdemacros.h.in8
1 files changed, 4 insertions, 4 deletions
diff --git a/kdecore/kdemacros.h.in b/kdecore/kdemacros.h.in
index 00f49bbd7..2edb4ee3a 100644
--- a/kdecore/kdemacros.h.in
+++ b/kdecore/kdemacros.h.in
@@ -53,8 +53,8 @@
* cope with symbol visibility.
*/
#define KDE_Q_EXPORT_PLUGIN(PLUGIN) \
- Q_EXTERN_C KDE_EXPORT const char* qt_ucm_query_verification_data(); \
- Q_EXTERN_C KDE_EXPORT QUnknownInterface* ucm_instantiate(); \
+ Q_EXTERN_C KDE_EXPORT const char* tqt_ucm_query_verification_data(); \
+ Q_EXTERN_C KDE_EXPORT TQUnknownInterface* ucm_instantiate(); \
Q_EXPORT_PLUGIN(PLUGIN)
/**
@@ -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 moc-generated code. In any case,
+ * other signals; they get invoked from tqmoc-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
- * moc code as well and thus the warnings are useless.
+ * tqmoc code as well and thus the warnings are useless.
*
* \par
* Also note that it is not possible to use KDE_DEPRECATED for classes which