comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » IDLDoc Bandwagon
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDLDoc Bandwagon [message #72655 is a reply to message #72510] Mon, 20 September 2010 21:20 Go to previous messageGo to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Michael Galloy writes:

> But, in the meantime, you are correct, the FORMAT_STYLE and MARKUP_STYLE
> determine how the comments are formatted in the output. Looking at some
> of the code in your library, it looks like you probably should use
> FORMAT_STYLE='IDL' and MARKUP_STYLE='preformatted' (it won't look good,
> but should be readable). The MARKUP_STYLE='preformatted' will make
> linefeeds significant.

I have finally managed to get something that looks hopeful,
but, yes, it took me quite a while to find the right page
with the information I needed. I think the new documentation
will be well received. :-)

> You will also need to make the comment header
> (i.e., the part between ;+ and ;-) be next to the routine prototype (the
> pro/function line), like:

Yes, I have a question about that. What do you do in the
case of a large file with many modules? The module I want
to document is, of course, at the bottom of the file. And
yet I want the documentation to appear at the top of the
file. How would you handle something like that?

Also, I want to have the copyright notice (as some significant
amount of text) in the file. What would be the best way to
handle that? There really isn't a category for that, and
it seems a little strange to put it someplace like after
the procedure definition statement (which would follow
immediately after the documentation) and before the first
line of code in the procedure.

The copyright thing is on my mind today, as I am in the
process of moving the Coyote and Catalyst Libraries over
to GoogleCode, so people can access it via a Subversion
repository.

Thanks for the help!

Cheers,

David



--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: The variable shellCmd is not defined
Next Topic: Coyote and Catalyst Libraries Available on SVN Repository

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 11:21:55 PDT 2025

Total time taken to generate the page: 1.12182 seconds