mac: Remove one static initializer.

mac: Remove one static initializer.

The NSAccessibility* strings are not defined, only declared,
in NSAccessibility.h, so the compiler needs to emit a static initializer
if they are used in a global initializer.

BUG=94925
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=148914

[Nico, 2012-07-29 06:07:54]

First to review wins!

[Nico, 2012-07-29 06:09:06]

https://chromiumcodereview.appspot.com/10821085/diff/1/content/browser/access...
File content/browser/accessibility/browser_accessibility_cocoa.mm (right):

https://chromiumcodereview.appspot.com/10821085/diff/1/content/browser/access...
content/browser/accessibility/browser_accessibility_cocoa.mm:248: +
(void)initialize {
(+initialize methods are effectively static initializers too, but it's still
better to have 1 instead of 2 of those :-) )

[dmazzoni, 2012-07-29 06:30:45]

lgtm

Great. I could be wrong, but I think this is even better that you suggest
because the static +initialize method won't be called until the first message is
sent to an instance of this class - so if accessibility is never enabled, the
static initializer will never run.

[commit-bot: I haz the power, 2012-07-29 15:47:48]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/thakis@chromium.org/10821085/1