>> What I want is not a nifty
>> editor function. I want something that will read in my
>> source code and produce something like this:
>>
>> Procedure A calls:
>> B
>> C
>> D
>> ...
>I don't think the compiler will do this. In fact, the compiler doesn't
>even have this information in the normal course of doing its job. Not
>that the linker will export the information either.
A compiler certainly COULD track this information! It definitely DOES
know which procedures call which others.
>If you know perl, it's probably a few hours work. Care to share it when
>you're done? :-)
Unfortunately, I don't know perl.... :-(
>> Another "nice-to-have" that most compilers generate is a
>> list of variables used. That's a good way to ensure that
>> you don't have any variables that are not used.
>The -Wall flag to gcc will warn about unused variables.
Thanks, I'll give that a shot!
>> I can't find an option in GCC to do either of these two
>> things, both of which are commonly provided by compilers :-(
>Commonly by *what* compilers? I've used several (for C/C++ and java)
>on the four most common platforms and have never seen the first
>feature. Not that I'd mind the feature....
Well, I guess my mainframe background is showing here. But the PL/I,
FORTRAN, Pascal, and I think even (shudder) COBOL compilers
that I've used all could do this. Say what you want about IBM, but
they make good compilers :-) Oh well.....
Tom Ward
