dummzeuch

Yes, I noticed that one. Thanks. I haven't got the rights to grant svn write access on the GExperts project on source forge. But if you send me a patch I will commit the changes.

There would be quite a lot of useful things that could be done if there was an up to date parser for Delphi code. Unfortunately there apparently isn't. I tried to update Martin Waldenburg's parser, which is used in GExperts, but it's just not easy to do. The Castalia parser, which is based on MW's parser unfortunately is incompatible in too many places to use as a replacement without too many changes. But by the look of it, it supports more recent language constructs. It's still not complete though, and definitely doesn't support the latest additions.

The GExperts Grep Search expert has various options to tell it which files to search: The current file All files in project All files in project group A directory list (separated by semicolon) That sounds like an exhaustive list, but it isn’t. Both, project and project group, were only searching files explicitly listed in the project(s). Files that were linked into the project using the search path, were not searched. Until now, that is: There is now an option to use the MAP file instead of the DPR file for project search. https://blog.dummzeuch.de/2019/03/03/gexperts-grep-can-use-the-map-file/

I always build 3rd party sources with the project. That's the only way I can be sure that the executable is based on the code it is supposed to be. And since compile times in Delphi are really short, it doesn't have any drawbacks in my opinion.

Kick those lazy bastards into the ass! 😉 As a workaround you could add a {$warnings off} and {$hints off} into theses 3rd party units.

What do you mean by "log filled with various warnings"? Do you really have more than a hand full? That's the first thing I kick a coworker's ass for, if it gehts checked in to SCM. OK, a possible solution would be to configure these hints / warnings you are really interested into be errors in the project configuration -> Building -> Delphi Compiler -> Hints and Warnings. edit: Apparently that's not possible for hints but only for warnings.

The map file lists all units that have been linked into the executable. So it is the easiest way to get a list of these units. Grep then uses the same algorithm as the Uses Clause Manager's identifier tab to find the source code for these units. That algorithm uses the project (as the first step) and all configured search paths (including the browsing path as the last step), so it should find the same source code as the compiler / linker does.

Not a bug. ToolsApi.pas is not in the search path (only ToolsApi.dcu), so it isn't parsed. You can see that in the Unit Uses list of GX_About: There is no Location info for that unit because it cannot be found. OK, that means that the list of indirect depencencies is not complete, because it does not contain units that are only in the uses list of units that are not in the search path. Hm, not sure I like that.

Possibly a bug

... and then you switch to the "indirect dependencies" tab and ... ?

That list already contained all used units, including those indirectly used. And the list for the project (root node in the tree) contains all units of the project.

Was already used, that was the first thing I checked.

Done. I even improved performance of the indirect list by a factor of about 5 to 10 (I didn't do any exact timing on the original code, so I don't know. But it now takes less than 2 seconds for the GExperts project where before it took more than 10.) Note to self: If the performance of some code is bad, check whether it stores and accesses data in the UI all the time. Remove this access and watch the performance skyrocket. Another note to self: TListView is one of the worst performing controls out there. If you want to improve performance further, use a TStringList or maybe even better a virtual string list.

@mael Which Delphi version are you using? And what does the GExperts -> Keyboard Shortcuts expert show for Alt+Ctrl+C on your installation? Please answer on https://sourceforge.net/p/gexperts/bugs/114/

@PeterPanettone Isn't GExperts -> Project Dependencies what you are looking for? The only shortcoming is that it does not list the indirect dependencies for the whole project, into which I am looking right now. If it's possible to be done easily, I will add that.

I cannot reproduce this in Delphi 2007. Which Delphi version are you using? And what does the GExperts -> Keyboard Shortcuts expert show for Alt+Ctrl+C on your installation? Please answer on https://sourceforge.net/p/gexperts/bugs/114/

If it's not available with full source code, I'm not going to buy it. I have been burned twice with buying components / libraries in binary form only where the company went bust a few years later. Apart from that I like the idea of using SVG for graphics a lot. It would solve several problems I am currently facing.

There are now two experimental options for searching forms that address these issues at least for standard components. The output still needs some polishing.

I think the symbols are a good idea. But why the plus an minus? In the contents tree they signal that you can expand the node (I guess, I haven't installed you tool on this computer). Since the colours are quite easy to distinguish, use the circles without the plus / minus characters.

For the user: yes, for the programmer: no.

For which again you would want to get a complete list, including those units indirectly used.

You can't. Why would you want to? I can only think of a few uses for such a list: Check if a unit is added that should not (e.g. it is being phased out / deprecated) Get a list of 3rd party components to e.g. add to an about box (But that is better done at runtime.) Search all used units for some string (What GExperts Grep now does and the GExperts Open File has been doing for a while) All of these would want to include units that were indirectly added to a project. (I know, I am a bit late to the conversation)

So the idea is simply to get a list of all units linked into the project? That can be done by parsing the map file, if one is being created. And that's a lot easier and faster.

HKLM\Software\WOW6432Node\Embarcadero\BDS\<version>\Library\* and a copy for each user under HKCU\Software\Embarcadero\BDS\<version>\Library\* The latter is the one edited in the Tools -> Options dialog.

Please file a bug report on SourceForge.