Implementation of MessagePump for Mojo.
I've refactored a bunch of the common MessagePump code into
message_pump_test. This allows us to share tests for custom
messagePumps and should allow moving MessagePumpForUI out later
on. Sadly it results in a ginormous macro. On the positive side it's
easy to use.
BUG=none
TEST=none
R=darin@chromium.org
Review URL: https://codereview.chromium.org/66193007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@234540 0039d316-1c4b-4281-b951-d872f2087c98
CrOS-Libchrome-Original-Commit: 3fee57b39da2e99e44d65021263d057a7b239683
diff --git a/base/message_loop/message_loop.h b/base/message_loop/message_loop.h
index 84e1449..e307d36 100644
--- a/base/message_loop/message_loop.h
+++ b/base/message_loop/message_loop.h
@@ -163,6 +163,12 @@
// was successfully registered.
static bool InitMessagePumpForUIFactory(MessagePumpFactory* factory);
+ // Creates the default MessagePump based on |type|. Caller owns return
+ // value.
+ // TODO(sky): convert this and InitMessagePumpForUIFactory() to return a
+ // scoped_ptr.
+ static MessagePump* CreateMessagePumpForType(Type type);
+
// A DestructionObserver is notified when the current MessageLoop is being
// destroyed. These observers are notified prior to MessageLoop::current()
// being changed to return NULL. This gives interested parties the chance to