Also I kind of assumed with the code that all the includes are uniquely named and don't do anything special about the duplicates. The first found header with the given name "wins".

I think this assumption easily breaks down on larger (maybe proprietary) code bases. Perhaps we can improve by looking for common tags (tags for function declarations must match with the source file in question right?) but not necessarily in this PR.

Agree that include path clashes is not uncommon, especially for portable software that has multiple backends, and therefore multiple versions of the same include. Can we use the path instead of just the name, presumably that is handled since Geany can open two files of the same name and symbols don't get mixed up (hopefully can't try ATM). That should be unique unless a global tags file overlaps local files.

Also agree that this PR should be kept simple, just make an issue for remembering it and do later.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.