Neither of these examples is particularly complex or requiring a makefile rule solver to resolve. Both Evan and Nick's examples are one component depending on one other component. I would call that a "simple" dependency that is easy to document in a comment and to maintain correctly when editing the code. Neither of these examples required modifying any other parts of startup, much less "complex reorganization," to satisfy their requirements.
Brett On Thu, Jan 15, 2009 at 4:10 PM, Evan Martin <e...@chromium.org> wrote: > > On Thu, Jan 15, 2009 at 3:06 PM, Brett Wilson <bre...@chromium.org> wrote: >> >> On Thu, Jan 15, 2009 at 2:06 PM, Erik Kay <erik...@chromium.org> wrote: >>> The issue is one of maintenance. A lot happens at startup. As people >>> make changes, it's not necessarily obvious where to insert your >>> initialization code. Depending on your dependencies, your new service >>> may require a complex re-ordering of initialization. If we actually >>> explicitly express dependencies and automatically manage them, then we >>> can be precise about it. >> >> I'm still a bit skeptical of how complex these dependencies are. Can >> somebody give an example of such a service that required complex >> interdependencies on startup and required very specific ordering? > > Another one > http://src.chromium.org/viewvc/chrome?view=rev&revision=5069 > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
