On Tue, Jan 13, 2009 at 11:56 PM, Ben Goodger (Google) <[email protected]>wrote:
> It looks like everyone and their dog adds init code to the startup > sequence. This takes the form of first time initialization, command > line switch parsing, etc. Is there any special reason why it's done in > the startup flow vs. in a static method the first time a service is > created or used? All I know is there are lots of ordering dependencies, where certain classes must be initialized before others. Most of these are subtle and undocumented :( Even besides the methods you named, there are a slew of other initialization methods whose purpose is wildly unclear. When adding support for --user-agent=, I tried to understand some of this stuff better with jam's help and came to the conclusion that a lot of it was insane and should be condensed, redesigned entirely, etc. If you're cleaning up startup, definitely also look at the methods I touched when adding that switch too (a lot of them might be better places for stuff that lives in BrowserMain). PK --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
