Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!randvax!segue!jim
From: jim@segue.segue.com (Jim Balter)
Newsgroups: comp.unix.programmer
Subject: Re: function tree trace for a.out's ?
Message-ID: <7205@segue.segue.com>
Date: 21 Apr 91 22:27:36 GMT
References: <1991Apr8.115049.5485@ohm.york.ac.uk> <1991Apr19.150727.17125@ghost.unimi.it> <1991Apr20.171557.19792@NCoast.ORG>
Reply-To: jim@segue.segue.com (Jim Balter)
Organization: Segue Software, Inc. - Santa Monica, CA. +1-213-453-2161
Lines: 10

In article <1991Apr20.171557.19792@NCoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery KB8JRR/AA) writes:
>If (and only if) you adhere to a one-function-per-source-file scheme, you can
>do this by treating "U" lines as refs and others as defs.  If you have
>multiple functions per file, you lose:  you can't localize it by function,
>only by file.

Nope.  Executables don't contain unresolved references ('"U" lines').
And in .o's, the unresolved references are bracketed by the function
definitions and thus the call structure is determinable, and cflow does it.
Number of functions per file is irrelevant.