engine: eliminate virtual checkForSuspend/Abort()

Since the introduction of SuspendFlags, the ony remaining user
of the virtual aspect of checkForSuspend/checkForAbort() was the
testing code. By using the suspend/abort request mechanism in
SuspendFlags, it becomes possible to move checkForSuspend/Abort()
into SuspendFlags itself.

This will be useful to use it outside of a SyncContext member.

1 files changed, 2 insertions, 5 deletions

diff --git a/src/client-test-app.cpp b/src/client-test-app.cpp
index f2607bbc..c0a13f1c 100644
--- a/src/client-test-app.cpp
+++ b/src/client-test-app.cpp
@@ -382,7 +382,7 @@ public:
                 SyncContext::prepare();
                 if (m_options.m_prepareCallback &&
                     m_options.m_prepareCallback(*this, m_options)) {
-                    m_options.m_isAborted = true;
+                    m_options.m_isAborted = SuspendFlags::getSuspendFlags().abort();
                 }
             }
 
@@ -392,14 +392,11 @@ public:
                 if (!m_started) {
                     m_started = true;
                     if (m_options.m_startCallback(*this, m_options)) {
-                        m_options.m_isAborted = true;
+                        m_options.m_isAborted = SuspendFlags::getSuspendFlags().abort();
                     }
                 }
             }
 
-            virtual bool checkForAbort() { return m_options.m_isAborted; }
-            virtual bool checkForSuspend() {return m_options.m_isSuspended;}
-
             virtual boost::shared_ptr<TransportAgent> createTransportAgent()
             {
                 boost::shared_ptr<TransportAgent>wrapper = m_options.m_transport;