From: Kent Hansen <kent.hansen@nokia.com>
Date: Sun, 27 May 2012 20:21:23 +0000 (+0200)
Subject: Don't call metaObject()->method() redundantly
X-Git-Tag: 071012110112~691
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d0c0360392af121985e314c8894089c12761e522;p=profile%2Fivi%2Fqtbase.git

Don't call metaObject()->method() redundantly

The desired method is already stored in a local variable.

Change-Id: Ibf0078813c7aebc83604b9c7ad9a8b6c596c5c65
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
---

diff --git a/src/corelib/statemachine/qstatemachine.cpp b/src/corelib/statemachine/qstatemachine.cpp
index 69d469e..fffe6de 100644
--- a/src/corelib/statemachine/qstatemachine.cpp
+++ b/src/corelib/statemachine/qstatemachine.cpp
@@ -1657,7 +1657,7 @@ void QStateMachinePrivate::handleTransitionSignal(QObject *sender, int signalInd
 
 #ifdef QSTATEMACHINE_DEBUG
     qDebug() << q_func() << ": sending signal event ( sender =" << sender
-             << ", signal =" << sender->metaObject()->method(signalIndex).methodSignature().constData() << ')';
+             << ", signal =" << method.methodSignature().constData() << ')';
 #endif
     postInternalEvent(new QStateMachine::SignalEvent(sender, signalIndex, vargs));
     processEvents(DirectProcessing);