| Re: Displaying Programs [message #38242] |
Fri, 27 February 2004 07:44 |
Ben Panter
Messages: 102
Registered: July 2003
|
Senior Member |
|
|
David Fanning wrote:
> Ben Panter writes:
>
>
>> I've got a large group of procedures and functions which I inherited
>> from a collaborator - about 20-30 which share various common blocks
>> (yuck!) and rely on each other to operate a data compression and
>> analysis algorithm. For a couple of years I've added to it and modified
>> it, but I'm starting to loose track of where everything is and what
>> everything does.
>>
>> I'd really like to be able to make some sort of diagram out of the
>> code, which highlights what depends on what, which programs are exposed
>> to which common blocks and what each procedure does for a quick reference.
>
>
> What I do for this kind of diagram is cook up a big
> pot of spaghetti and throw it against the wall. :-)
Looking at my current masterpiece I think the results would be fairly
similar although the adaptive cross-linking slide aspect could be
enlightening... :-)
>> At the moment I'm doing this with a pen and a large sheet of paper,
>> but it occured to me that all the information I am trying to put down is
>> already in the headers [they're in the standard(?) format followed by
>> astrolib and coyote].
>>
>> Does anyone know of an automated method for a) extracting this data
>> and b) displaying it?
>
>
> MK_HTML_HELP is what I use.
Thanks David, I'll go and have a play with that.
Ben
--
Ben Panter, Edinburgh
My name (no spaces)@bigfoot which is a com.
|
|
|
|
| Re: Displaying Programs [message #38249 is a reply to message #38242] |
Fri, 27 February 2004 06:10  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Ben Panter writes:
> I've got a large group of procedures and functions which I inherited
> from a collaborator - about 20-30 which share various common blocks
> (yuck!) and rely on each other to operate a data compression and
> analysis algorithm. For a couple of years I've added to it and modified
> it, but I'm starting to loose track of where everything is and what
> everything does.
>
> I'd really like to be able to make some sort of diagram out of the
> code, which highlights what depends on what, which programs are exposed
> to which common blocks and what each procedure does for a quick reference.
What I do for this kind of diagram is cook up a big
pot of spaghetti and throw it against the wall. :-)
> At the moment I'm doing this with a pen and a large sheet of paper,
> but it occured to me that all the information I am trying to put down is
> already in the headers [they're in the standard(?) format followed by
> astrolib and coyote].
>
> Does anyone know of an automated method for a) extracting this data
> and b) displaying it?
MK_HTML_HELP is what I use.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
