diff options
| author | pliard@chromium.org <pliard@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-30 12:13:28 +0000 |
|---|---|---|
| committer | pliard@chromium.org <pliard@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-30 12:13:28 +0000 |
| commit | 7f09ee436f706a22b254d3fee7eb20beb53fdad8 (patch) | |
| tree | 5e56d40ab8f68524220d3f19c808e01d1e3fecd6 /tools/json_to_struct | |
| parent | 672346f283ee7946a5d1dea1b0a0152a5ceafeea (diff) | |
| download | chromium_src-7f09ee436f706a22b254d3fee7eb20beb53fdad8.zip chromium_src-7f09ee436f706a22b254d3fee7eb20beb53fdad8.tar.gz chromium_src-7f09ee436f706a22b254d3fee7eb20beb53fdad8.tar.bz2 | |
Remove Thread wrapper class in forwarder2.
This class unnecessarily reinvented the wheel in a non-RAII way that proved to
be harmful (see r210830).
Also, this class wasn't playing nicely with Chromium's base idioms. For
instance it was impossible to do task posting with it. This implied some
non-idiomatic threading code that was hard to read and reason about (e.g. using
locks, pthread_condition_t...) thus hard to maintain and debug. See
device_listener.cc for instance.
This CL also refactors the shutdown code to ensure that in general all the
objects are always destroyed on the thread they were created on. This wasn't
the case before.
BUG=242846
R=bulach@chromium.org, digit@google.com
Review URL: https://codereview.chromium.org/19478003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214338 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/json_to_struct')
0 files changed, 0 insertions, 0 deletions