Whole Tomato Software Forums - Show Include Chain to Definition

Whole Tomato Software Forums

User name:	Password:
Save Password
Forgot your password?

All Forums

Visual Assist

Feature Requests

Show Include Chain to Definition

New Topic

Reply to Topic

Printer Friendly

Author

Topic

jay.carlton
Ketchup Master

USA
65 Posts

Posted - Oct 15 2013 : 11:30:27 AM

Hi,

VA X is very good at traversing the #include hierarchy when I do Goto. What I'm interested in is, for those cases where there are more than one inclusions in the symbol's journey from its source to its point of use, would there be a way to have VAX display the include trace? So if a type type1 is used in b.cpp, which includes b.h which includes something else that eventually includes a.h, I'd want to be able to right click on type1 in a.cpp and ask VA X to trace this path through the include graph for me. The output could be something like


type1 in b.cpp
-->c:\\project\\include\\b.h
-->c:\\project\\include\\a1.h
-->c:\\common\\a.h

In cases where project settings force the inclusion, that might be nice as well.

Thanks, and have a great day.

-Jay

feline
Whole Tomato Software

United Kingdom
18943 Posts

Posted - Oct 15 2013 : 10:38:00 PM

An interesting idea, I rather like this. I have put in a feature request to see what our developers make of it:

case=77655

I don't follow your comment about project settings forcing the inclusion though. If the definition for a symbol is not ultimately included then this is a compiler error in the making, and Add Include is designed to help here:

http://www.wholetomato.com/products/features/autoUsing.asp

zen is the art of being at one with the two'ness

jay.carlton
Ketchup Master

USA
65 Posts

Posted - Oct 16 2013 : 09:04:09 AM

I wasn't clear in my head on which project settings might make a difference, and now that I think about it, I can't think of any off the top of my head. I suppose you can add eligible include directories or set precompiler symbols and macros that change what gets included, but if it shows the path(s) consistently with how VA X sees them after accounting for precompiler directives, then that would help resolve ambiguities. An option to show which line in what file #included each file would help in those rare cases if that information is readily available.

-Jay