I don't know how many interdependencies we have--I was relying on
ben's "everyone and their dog" assessment :-). That said, I write a
makefile (or equivalent) for anything with >2 source files, so writing
the dependencies in code rather than comments doesn't strike me as a
large cost.
--Amanda
On Thu, Jan 15, 2009 at 4:37 PM, Brett Wilson <bre...@chromium.org> wrote:
>
> On Thu, Jan 15, 2009 at 1:19 PM, Amanda Walker <ama...@chromium.org> wrote:
>>
>> That's true. In the example I gave (Mac driver loading), each module
>> has a property list that lists its dependencies (and version
>> requirements, etc.). That's not quite as simple to do inside a single
>> application, of course, but having code do the ordering still seems
>> like a win to me.
>>
>> Consider startup as a sequence of, say:
>>
>> Initializer foo("foo");
>> foo.DependsOn("bar");
>> foo.DependsOn("zot");
>>
>> Initializer alice("alice");
>> alice.DependsOn("bob");
>> alice.DependsOn("eve");
>> [...]
>> Initializer::LaunchAll();
>>
>> (or, more generally, "Initializer:::Launch("chromium");" where
>> "chromium" is a top level module, so that the general framework could
>> be used for things besides app launch)
>
> I have a hard time thinking about this with your abstract example. I
> also have a hard time believing we have so many interdependencies that
> it requires writing a makefile to start the program, and that such a
> syntax is easier to read than just listing out in comments why things
> are done in this order.
>
> Brett
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
