namespace {} trick for SK_DECLARE_STATIC_ONCE

namespace {} trick for SK_DECLARE_STATIC_ONCE

Like all our other SK_DECLARE_STATIC_*, it's usually not a thread-safe
thing to put inside a function.  Adding namespace {} prevents that
syntactically.

Needs https://codereview.chromium.org/841263004/ to land first.

BUG=chromium:447890
No public API changes.
TBR=reed@google.com

Committed: https://skia.googlesource.com/skia/+/199ba8e19b0cafb37eea3beab162bc4b52728fff

[mtklein, 2015-01-12 19:22:25]

mtklein@google.com changed reviewers:
+ bungeman@google.com, mtklein@google.com

[bungeman-skia, 2015-01-12 19:36:37]

lgtm, with one nitish.

https://codereview.chromium.org/806473006/diff/1/src/utils/win/SkDWrite.cpp
File src/utils/win/SkDWrite.cpp (right):

https://codereview.chromium.org/806473006/diff/1/src/utils/win/SkDWrite.cpp#n...
src/utils/win/SkDWrite.cpp:44: SK_DECLARE_STATIC_ONCE(once);
'once' seems like a rather generic thing to put at global scope like this, but I
don't see any good reason to change it... ('gOnce' isn't really any better). It
was quite nice when these were scoped.

[mtklein, 2015-01-13 15:28:57]

>
https://codereview.chromium.org/806473006/diff/1/src/utils/win/SkDWrite.cpp#n...
> src/utils/win/SkDWrite.cpp:44: SK_DECLARE_STATIC_ONCE(once);
> 'once' seems like a rather generic thing to put at global scope like this, but
I
> don't see any good reason to change it... ('gOnce' isn't really any better).
It
> was quite nice when these were scoped.

Agreed.  I was also not sure what I'd change the name to, so I left it.  I'm
hoping its proximity makes things obvious.

[mtklein, 2015-01-13 16:24:41]

The CQ bit was checked by mtklein@google.com

[commit-bot: I haz the power, 2015-01-13 16:25:30]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/806473006/1

[commit-bot: I haz the power, 2015-01-13 16:40:27]

Committed patchset #1 (id:1) as
https://skia.googlesource.com/skia/+/199ba8e19b0cafb37eea3beab162bc4b52728fff