On Tue, 24 Mar 2015 16:39:09 +0100 (CET) Michael Van Canneyt <[email protected]> wrote:
>[...] > > Why? It is a very useful feature. > > I don't see how. Some IDE functions added dependencies automatically, creating redundant dependencies. The clean up function allows to remedy this. > IMHO it is even wrong, because I want to see explicitly all dependencies > added to a package/project. Removing the "clean up" function will not help here. Maybe the project inspector can be extended to show indirectly used packages, so you can see all dependencies. > Package A (unitA) depends on Package B (UnitA uses unitB) and Package C > (UnitA uses unitC). > Package B depends on Package C (unitB uses unitC). > Invoking the dialog in A will propose to remove the C from the dependencies > of A (transitivity). > That is IMHO not wanted. If I remove the depencency on B (no longer use > UnitB) then the dependency > on C is lost. Hence, C must remain in the dependencies of A. If you remove the dependency A-B, then there is probably a reason for that. For example A no longer works with B. Mattias -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
