diff options
| author | viettrungluu@chromium.org <viettrungluu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-06-19 16:29:24 +0000 |
|---|---|---|
| committer | viettrungluu@chromium.org <viettrungluu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-06-19 16:29:24 +0000 |
| commit | 252e6603f3012cdc8de4a212999ef62660769be7 (patch) | |
| tree | a3cbc19e4153033c6383dcee6b546d07c72b6f89 /tools/gn | |
| parent | f6f6a0bbf76b719a933ee2ea4ee467cec241675a (diff) | |
| download | chromium_src-252e6603f3012cdc8de4a212999ef62660769be7.zip chromium_src-252e6603f3012cdc8de4a212999ef62660769be7.tar.gz chromium_src-252e6603f3012cdc8de4a212999ef62660769be7.tar.bz2 | |
Mojo: Make GetDefault{AsyncWaiter,Logger} static methods of Environment.
Also:
* Move SetMinimumLogLevel() into MojoLogger itself. (This is somewhat
unfortunate, since may not be thread-safe -- in particular, when
sharing a copy of base's logging as in a component=shared_library
build, it becomes blatantly unsafe. Thus it's of slightly dubious
value. But it's where it belongs logically. Of course, sharing a log
level across applications that are cohabiting a process is dubious.
Avoiding this would mean at least layering a log level on top of
Chromium's.)
* Allow the (standalone) Environment's choices for default AsyncWaiter
and/or Logger to be overridden.
R=darin@chromium.org
Review URL: https://codereview.chromium.org/339403003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278401 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/gn')
0 files changed, 0 insertions, 0 deletions