Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Ok, clearly the best is:
/A/B/C1/include/header.hpp
Ok, let's hard-code that path and the problem's solved forever ;-).
With your Something backend example the problem isn't so big because at least the member names are identical so non-scope autocompletion is going to work (of course scope autocompletion for h could be a problem).
What might be a bigger problem is some utils.h created at various places with different utility functions for say different submodules. Here the path-based heuristic I suggested or the @kugel- 's tag-similarity-based heuristic might work.
Anyway, the worst case that happens is that tags won't be sorted in the most optimal way which can however happen for many other reasons so right now I'd suggest to just keep the implementation simple and possibly improve it in the future.
I guess an associated question would be what would happen if both the declarations of Something are in the same file with an #ifdef deciding between them?
ctags extracts tags from both branches.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.