Update {virtual,override,final} for components/ to follow C++11 style.

components/policy/core/common/policy_loader_mac_unittest.cc

Index: components/policy/core/common/policy_loader_mac_unittest.cc
diff --git a/components/policy/core/common/policy_loader_mac_unittest.cc b/components/policy/core/common/policy_loader_mac_unittest.cc
index a840724d937cbb21f60919dfd87748598a4740eb..3fcc78502abb834702b0ba2792ab86d55c4b2cc8 100644
--- a/components/policy/core/common/policy_loader_mac_unittest.cc
+++ b/components/policy/core/common/policy_loader_mac_unittest.cc
@@ -137,9 +137,8 @@ class PolicyLoaderMacTest : public PolicyTestBase {
  protected:
   PolicyLoaderMacTest()
       : prefs_(new MockPreferences()) {}
-  virtual ~PolicyLoaderMacTest() {}

[erikwright (departed), 2015/01/09 21:06:51]

Chromium guidelines encourage consistent declaration of destructors for all
non-POD objects, even when declared in a .cc file.

http://www.chromium.org/developers/coding-style/cpp-dos-and-donts#TOC-When-yo....

[dcheng, 2015/01/09 22:09:32]

The reason we declare them is so we can define them out-of-line, to potentially
avoid destructor bloat. This declaration is inline as it is, so there is no
difference between explicitly declaring it and letting the compiler emit an
implicit one.

[Mattias Nissler (ping if slow), 2015/01/13 10:03:13]

The reason this dtor is here is actually because the rule is all classes with
virtual functions should have a virtual dtor. We often waive that rule for
tests. I don't feel strong on this.

[erikwright (departed), 2015/01/13 12:03:27]

I re-read C++ Dos and Don'ts, "What about code outside of headers?":

"it's still wise to follow the above guidelines... Being in a consistent habit
everywhere reduces the risk of making mistakes, and results in more consistent
code... "

Which is what I had based my earlier comment on. But then I kept reading:

"For testing code, most of these factors are reduced or eliminated ...
Ultimately, test file inlining should be a readability-focused judgment call on
the part of the test author and reviewer."

Which seems to apply to this case.

 
-  virtual void SetUp() override {
+  void SetUp() override {
     PolicyTestBase::SetUp();
     scoped_ptr<AsyncPolicyLoader> loader(new PolicyLoaderMac(
         loop_.message_loop_proxy(), base::FilePath(), prefs_));
@@ -147,7 +146,7 @@ class PolicyLoaderMacTest : public PolicyTestBase {
     provider_->Init(&schema_registry_);
   }
 
-  virtual void TearDown() override {
+  void TearDown() override {
     provider_->Shutdown();
     PolicyTestBase::TearDown();
   }