Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!rice!sun-spots-request
From: quasar@flash.bellcore.com (Laurence R. Brothers)
Newsgroups: comp.sys.sun
Subject: Re: Problems with cxref in 4.0.3...any fixes?
Keywords: Miscellaneous
Message-ID: <1990Oct7.223243.27474@rice.edu>
Date: 7 Oct 90 21:30:00 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 10
Approved: Sun-Spots@rice.edu
Originator: spots@walhalla.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 321, message 3

I have had the unsettling experience of having about 25% of valid
compilable c code kill cxref. Can anyone recommend a better stand-alone
cross-referencer? I want to know where each identifier is declared,
defined, and used. It would be nice to know whether a usage was on the lhs
or rhs. Oh, and a parse tree and symbol table wouldn't hurt. Hmm, I really
want everything a compiler does, short of code generation, and bared to
the world through readable ascii output.

	         Laurence R. Brothers (quasar@bellcore.com)
      Bellcore -- Computer Technology Transfer -- Knowledge-Based Systems