Reduce number of unnamed-type-template-args violations.

chrome/browser/ui/webui/options/certificate_manager_handler.cc

Index: chrome/browser/ui/webui/options/certificate_manager_handler.cc
===================================================================
--- chrome/browser/ui/webui/options/certificate_manager_handler.cc	(revision 97489)
+++ chrome/browser/ui/webui/options/certificate_manager_handler.cc	(working copy)
@@ -466,13 +466,12 @@
 
   int trust = certificate_manager_model_->cert_db().GetCertTrust(
       cert, net::CA_CERT);
-  using base::FundamentalValue;
-  FundamentalValue ssl_value(bool(trust & net::CertDatabase::TRUSTED_SSL));
-  FundamentalValue email_value(bool(trust & net::CertDatabase::TRUSTED_EMAIL));
-  FundamentalValue obj_sign_value(
-      bool(trust & net::CertDatabase::TRUSTED_OBJ_SIGN));
-  web_ui_->CallJavascriptFunction(
-      "CertificateEditCaTrustOverlay.populateTrust",
+  base::FundamentalValue ssl_value(!!(trust & net::CertDatabase::TRUSTED_SSL));

[Nico, 2011/08/19 20:34:23]

(I remember seeing !! for the first time in some open source project many years
ago, and it took me a month or so to figure out why it's not a no-op. I prefer
the explicit cast that was here before. But I don't feel too strongly about it.)

+  base::FundamentalValue email_value(
+      !!(trust & net::CertDatabase::TRUSTED_EMAIL));
+  base::FundamentalValue obj_sign_value(
+      !!(trust & net::CertDatabase::TRUSTED_OBJ_SIGN));
+  web_ui_->CallJavascriptFunction("CertificateEditCaTrustOverlay.populateTrust",
       ssl_value, email_value, obj_sign_value);
 }