RE: [bug-cflow] static function calls not being produced unless explicitly called

[Josiah Carlson (NIM)]

Sergey wrote:
> Josiah Carlson (NIM) <address@hidden> ha escrit:
> > I have recently started using cflow, and I have noticed that it
doesn't
> > produce static definition results in the call graph unless they are
> > explicitly called by a non-static function.
>
> It does not list any function (be it static or global), unless its
> invocation can be traced up to main function (either `main' or
whatever
> given with the `--main' command line option). 
>
> > Personally, I want to see all static functions in the output.  I
have
> > worked around it by temporarily removing the static portion of the
> > declaration,
>
> Removing the static qualifier in your example does not change anything
> (if it does, then it is a bug). The only thing that matters is whether
> `foo' is called from `main' or not.

Running variants of the example I sent previously does not seem to show
the behavior I am experiencing when running it on a group of 20 or so
.c/.h files.

Though by your description of cflow's behavior, I shouldn't be seeing
any output, as none of the source files I am running cflow on have any
main function (they are all Python extension modules), nor have I been
passing anything with --main (unless something magical happens when you
do something like 'cflow *.[ch]' ).

I guess to get the behavior I desire I will have to change cflow to suit
my needs.  Thank you for your help Sergey,

 - Josiah