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, 1 insertions, 1 deletions

diff --git a/test/ClientTest.cpp b/test/ClientTest.cpp
index 305ea27d..e6e8c285 100644
--- a/test/ClientTest.cpp
+++ b/test/ClientTest.cpp
@@ -5329,7 +5329,7 @@ public:
             m_messageCount++;
             if (m_interruptAtMessage >= 0 &&
                     m_messageCount > m_interruptAtMessage) {
-                m_options->m_isSuspended = true;
+                m_options->m_isSuspended = SuspendFlags::getSuspendFlags().suspend();
             }
             m_wrappedAgent->getReply(data, len, contentType);
         }