Noissue - Remove a dead inheritance and some dead code

src/plugin/PluginTabBase.cpp

Index: src/plugin/PluginTabBase.cpp
===================================================================
--- a/src/plugin/PluginTabBase.cpp
+++ b/src/plugin/PluginTabBase.cpp
@@ -27,11 +27,6 @@
 #include <dispex.h>
 #include <Mshtmhst.h>
 
-int CPluginTabBase::s_dictionaryVersion = 0;
-int CPluginTabBase::s_settingsVersion = 1;
-int CPluginTabBase::s_filterVersion = 0;
-int CPluginTabBase::s_whitelistVersion = 0;
-
 CPluginTabBase::CPluginTabBase(CPluginClass* plugin)
   : m_plugin(plugin)
   , m_isActivated(false)
@@ -312,6 +307,10 @@
   m_criticalSectionCache.Unlock();
 }
 
+/*
+ * TODO: Replace the management of the log queue in this thread within CPluginTabBase
+ *       with a version of the log queue that uses a single internal worker thread.
+ */

[Eric, 2015/02/18 19:20:25]

I put this comment into the change set because the present changes (all
worthwhile in their own right) are also a prerequisite for accomplishing this
TODO, which has a number of benefits:

-- Change from one thread per tab to a single thread for the log queue.

-- Use notify/wait within the log queue rather than polling in multiple threads.

-- Eliminate CPluginTabBase member variables m_isActivate and
m_continueThreadRunning, whose only purpose is to manage the loop at the end of
this thread-main function. In turn this allows elimination of two entry points,
OnActivate and OnUpdate, whose only behavior is to refresh m_isActivate.

-- Further localize all the debug/log/trace/reporting capabilities.

I'm willing to replace this TODO comment with an issue in Trac, but if we do
that, we should have at least a bit of discussion beforehand to decide the scope
of the task.

[Oleksandr, 2015/02/27 10:59:27]

I'd vote for an issue instead of a TODO. Though I don't see any immediate need
in doing this at all. Even if we create an issue I'd vote for it to be P4 or
even P5.

[Eric, 2015/02/27 16:47:47]

https://issues.adblockplus.org/ticket/2058
I don't know of any really pressing need, but it would make finding the right
thread in the debugger easier.

It will also make combining CPluginTabBase and CPluginTab go easier, because
there will be less to combine.

 void CPluginTabBase::ThreadProc()
 {
   // Force loading/creation of settings
@@ -347,17 +346,7 @@
       DEBUG_THREAD("Loop iteration " + sTabLoopIteration);
     DEBUG_THREAD("--------------------------------------------------------------------------------")
 #endif
-      if (this->m_isActivated)
-      {
-        bool isChanged = false;
-
-        if (isChanged)
-        {
-          this->m_plugin->UpdateStatusBar();
-        }
-
-        this->m_isActivated = false;
-      }

[Eric, 2015/02/18 19:20:25]

I don't know where this code came from originally, but how does one not notice a
constant condition that you've just set on the previous line?

[Oleksandr, 2015/02/27 10:59:27]

Let's just say there was a lot of optimization happening here. Also, let's not
ever mention this, ok? Ever. :D

[Eric, 2015/02/27 16:47:47]

I promise I won't bookmark this URL and pull it out whenever I'm particularly
frustrated with code quality.

Really. I promise.

+      this->m_isActivated = false;
 
       // --------------------------------------------------------------------
       // End loop
@@ -368,9 +357,9 @@
       {
         // Post async plugin error
         CPluginError pluginError;
-        if (CPluginClient::PopFirstPluginError(pluginError))
+        if (LogQueue::PopFirstPluginError(pluginError))
         {
-          CPluginClient::LogPluginError(pluginError.GetErrorCode(), pluginError.GetErrorId(), pluginError.GetErrorSubid(), pluginError.GetErrorDescription(), true, pluginError.GetProcessId(), pluginError.GetThreadId());
+          LogQueue::LogPluginError(pluginError.GetErrorCode(), pluginError.GetErrorId(), pluginError.GetErrorSubid(), pluginError.GetErrorDescription(), true, pluginError.GetProcessId(), pluginError.GetThreadId());
         }
 
         // Non-hanging sleep