Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc.cso.uiuc.edu!garcon!garcon.cso.uiuc.edu!grunwald From: grunwald@flute.cs.uiuc.edu (Dirk Grunwald) Newsgroups: gnu.gcc Subject: protoize & tags Message-ID: Date: 24 Jun 89 04:01:27 GMT Reply-To: grunwald@flute.cs.uiuc.edu Distribution: gnu Organization: University of Illinois, Urbana-Champaign Lines: 28 the protoize package can be provide the framework for many other utilities. the best way to do this would be the option to produce a complete symbol table dump, listing all symbols, symbol classes, typedefs, etc etc. this information could be processed by other utilties, e.g., a modified protoize that doesn't require mods to the compiler itself. Another such utiliity would be an enhanced ``tags''. using the symbol table information, you could build a tags file that can be used for more sophisticated queries, e.g., scan through all functions, look for all local variables named `foo', whatever. also, such a tags program would be able to correctly grok C++ symbol names, something very difficult right now. it's unclear to me how much of this information could be gleaned from looking at the existing symbol table output generated using -g. That data doesn't make relations between e.g., line numbers & symbol names. in any case, providing a standardized symbol table dump utility would subsume the changes needed for protoize & serve other purposes too. -- Dirk Grunwald -- Univ. of Illinois (grunwald@flute.cs.uiuc.edu)