Code Analysis Issues

[Glenn9999]

An issue I've been having: One of my projects has been reaching into another directory unrelated to it to compile a few units that I copied over to this project to use. Now I don't see any references to this other directory anywhere, so how do I find out why Delphi is compiling something it shouldn't?

For that matter, is there any good way to get a top-down view of a project to see all the units and procedures/functions/objects/classes of those units and other resources and how they are getting used?

It is not possible for anyone to acknowledge truth when their salary depends on them not doing it.

 

[DjangMan]

GExperts has a project dependency checker that might be of use.

 

[majlumbo]

I've had the same issue with one of my applications. While debugging, it opened the main form of a completely unrelated program. After a while, I realized that the main form of both applications were named the same, and somehow, Delphi linked to the incorrect one (beats me as to why, since the correct one was in the same directory and the wrong one was in a completely different directory).

Now I'm a bit more selective on the name of my forms (especially my main form) to ensure there are no collisions with any other of my projects.

 

[djjd47130]

It has to do with the order of when Delphi finds these units. If for example you have a directory in your library path with one of the units with duplicate name as a unit in your project, I believe the library overrides whatever's in your project.

JD Solutions

 

[Glenn9999]

Okay, thanks for the advice. For what I'm working on, I definitely am on new ground given the size and scope of it.

It is not possible for anyone to acknowledge truth when their salary depends on them not doing it.