| Re: dependency tree / call graph in idl (cscope for idl)? [message #63802 is a reply to message #63673] |
Wed, 19 November 2008 10:34   |
Sven Utcke
Messages: 10
Registered: October 2007
|
Junior Member |
|
|
Paolo <pgrigis@gmail.com> writes:
> David Fanning wrote:
>> Sven Utcke writes:
>>
>>> what's the recommended way to do dependency tracking in IDL, you know,
>>> FUNCTION X depeneds on PRO Y which calls FUNCTIONs A, B, and C. That
>>> stuff. Preferably, but not necessarily from emacs?
>>>
>>> In C, I would for example use cscope <http://cscope.sourceforge.net/>.
>>>
>>> Reason I'm asking: I inherited a project with quite a few
>>> interdependent files (79 files so far, with 14000 lines, but I'm sure
>>> to find I missed some once dependency tracking works), and in order to
>>> get any idea at all what this is doing I would like to look at some
>>> sort of call graph.
>>>
>>> So what is the IDL-way of doing this?
>>
>> Whew! Don't you just hate it when someone comes to IDL for
>> the first time from a modern programming language. :-(
>
> This task may not even be *feasible* if the program does not
> consistently use square brackets for array!
Well, it might not be that bad. [c,e,idl]tags at least finds all
function and procedure definitions (although I would wish it would
also find each place where a function is called, but there). Would be
nice to also have global variables (which are used extensively within
the code in question --- is this good IDL praxis?), but I guess it
ought to be possible to hack [e,idl]tags to do that. But again this
leaves the problem of finding all uses...
Sven
--
___ _ _____ ___ Dr.-Ing. Sven Utcke ___ ___ _____ __
/ __| |/ / __| __| phone: +49 40 899-8-5317 | \| __/ __\ \ / /
| (_ | ' <\__ \__ \ fax : +49 40 899-4-5317 | |) | _|\__ \\ V /
\___|_|\_\___|___/ http://www.desy.de/~utcke (to come)|___/|___|___/ |_|
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
