Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!bu-cs!buengc!bph
From: bph@buengc.BU.EDU (Blair P. Houghton)
Newsgroups: comp.lang.c
Subject: Re: Search for a smarter C cross reference.
Message-ID: <3019@buengc.BU.EDU>
Date: 4 Jun 89 19:00:17 GMT
References: <4007@ima.ima.isc.com> <4020@ima.ima.isc.com>
Reply-To: bph@buengc.bu.edu (Blair P. Houghton)
Followup-To: comp.lang.c
Distribution: usa
Organization: Boston Univ. Col. of Eng.
Lines: 27

In article <4020@ima.ima.isc.com> mmengel@cuuxb.ATT.COM (Marc W. Mengel) writes:
>> ...  I would appreciate knowing of a similar xref for the C language...
>
>	If you compile a program with the -g option, and run "nm" on
>	it, you will get a raw listing of the base information you 

Yes, but...

Why does it list the functions I declared to "return" void as being type
int()?

My guess is that it's probably because our nm(1) (Encore Multimax; Umax)
is older than its cc(1), but I think it might also have something to do
with nm's assumptions about what is actually in the object-file, and there
might be something missing (like a tag that would disambiguate the type
of a function declared either void() or int()) from the object file.

Anyone got a little more insight on this?

				--Blair
				  "No doubt you are all thinking 'no
				   doubt about it'; but, no flame could
				   surprise me, educate me, or be of any
				   other value to me or the rest of the
				   world, so why would you bother?  Answer
				   the question and we can all get home in
				   time to kiss the kids goodnight."