idldoc
idldoc copied to clipboard
mgalloy
Documenting IDL code
It would be useful to be able to document several similar arguments on a single line. For example, it is common to see things such as: ``` ; :Params: ;...
Errors and warnings can be lost in the output from a large library. There should be a way to quiet the output to only show errors and warnings.
We have a huge legacy IDL library where most objects have been written with "get" and "set" as accessors and mutators. To stay consistent with that notation, it would be...
IDLdoc 3.5.1 will properly detect the fields "data" and "some_field". However, I'd like not only to see that "some_field" is "0L", but that "some_field" is set to "10L" (see second...
Links are currently displayed literally in LaTeX output, but should be made into hyperlinks.
When a class definition is splitted across multiple files, IDLDOC requires the ":Fields:" keyword to be present nowhere else other than in the descritpion of the "`__DEFINE`" procedure, but in...
IDLdoc should allow unrecognized headers as standard file/routine attributes and pass them through into the documentation. This request was originally from #51.
It would be very helpful when browsing documentation if we could specify related functions, classes, etc. to look at for more detail. IDLDoc already does a great job of linking...