Get rid of content::DidEndMainMessageLoop since it was declared in content but defined in chrome,...

content/browser/browser_main.cc

Index: content/browser/browser_main.cc
===================================================================
--- content/browser/browser_main.cc	(revision 101766)
+++ content/browser/browser_main.cc	(working copy)
@@ -167,6 +167,9 @@
 }
 
 BrowserMainParts::~BrowserMainParts() {
+#if defined(OS_WIN)

[willchan no longer on Chromium, 2011/09/19 21:52:49]

Looks to me like this should be in BrowserMainPartsWin. Same with the
OleInitialize() call below.

[jam, 2011/09/19 22:13:31]

BrowserMainPartsWin is in chrome, but we want this function for all embedders of
content, hence why it's here

[willchan no longer on Chromium, 2011/09/19 22:25:43]

Make sense. I suspect we should probably be created the content equivalents of
BrowserMainParts{Win|Mac|etc} eventually.

[jam, 2011/09/19 22:40:48]

I avoided that because Chrome also has its own platform versions, which derive
from a common chrome class. so if content also had 3 versions, we'd have to make
the base chrome one derive from three different classes depending on the
platform, which seemed a little hard on the eyes

+  OleUninitialize();
+#endif
 }
 
 void BrowserMainParts::EarlyInitialization() {