This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Pending setup patches (issue 6)

Igor Pechtchanski wrote:
> On Sun, 9 Mar 2003, Max Bowsher wrote:
>> But what about:
>> +    // TODO: free unused map entries
> Not a show-stopper.  Setup keeps all kinds of memory chunks around.
> They'll be freed when it exits anyway, it's just cleaner to explicitly
> manage them.

Fair enough.

>> +    // TODO: detect circular dependences
> Mmm, I think this one can be done later as an improvement.  Again,
> not a show stopper, just something that will influence the sort order.

Oh, ok, so at the moment, the order of execution of circular dependencies is
undefined? It won't get stuck in a loop, or anything terrible?

>> Also, dependences/dependencies: Both are valid words, but the 2nd
>> seems (to me) more commonly used?
> Must be my compiler background...  I'll change it if it bothers
> people.

That would be consistent with elsewhere in setup:        Dependency *dp = pkg.desired->required; DependencyProcessor {  DependencyProcessor (trusts const &aTrust, int
aDepth=0) :
                    deftrust (aTrust), depth (aDepth) {} (DependencyProcessor &processor, packagemeta
                    , packageversion const &aVersion) deftrust, size_t depth,
                    ecification *spec)  DependencyProcessor processor (deftrust, depth);       changed += processOneDependency (deftrust, depth,
                    + 1;       changed += processOneDependency (deftrust, depth,
                    + 1;


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]