IDLdoc 3.4.3 fixes the bug that prevented search results from being displayed.
michaelgalloy.com
Buy Modern IDL now!
Modern IDL offers IDL programmers one place to look for explanation, techniques, and reference material, for beginners and advanced users alike.
"... But I've always wanted a thorough, concise, up-to-date overview of the the IDL language and its vast capabilities. This is exactly what Mike's book provides in 464 very informative pages... Highly recommended!"
—Mort Canty
About me
I'm a software developer focusing on high-performance computing and visualization in scientific programming. I work mostly in IDL, but occasionally use C, CUDA, and Python.
I currently work for the National Center for Atmospheric Research (NCAR) at the Mauna Loa Solar Observatory. Previously, I worked for Tech-X Corporation, where I was the main developer for GPULib, a library of IDL bindings for GPU accelerated computation routines.
I am the creator and main developer for the open source projects IDLdoc, mgunit, and rIDL.
Contact me at Mastodon or via email at mgalloy at gmail dot com. For more details about me, see my CV/resume.
Need consulting/instruction? Contact me.
Other
- About + contact
- Books
- Simple Checklist
- Quantified Groceries
- Quantified Groceries Privacy Policy
- Simple Checklist Privacy Policy
- 1RM: Mac OS X Dashboard widget
March 1st, 2012 at 5:22 pm
Hey Mike,
I’ve been messing with templates to have IDLdoc generate a different sort of output file. Let’s say I have a loop such as
[[% FOREACH p IN parameters %][% SCOPE p %]
{…},
[% END %]]
Is there a magic template escape I can use to prevent the last “,” from appearing? I want my output to look like
[
{…},
{…}
]
instead of
[
{…},
{…},
]
Thanks,
Jim P.
March 1st, 2012 at 10:33 pm
No, there is no good way to do this in the template language. What I did in places like
profile.tt
was added asuffix
variable to each parameter/keyword object. This placed the burden on the parameter to know if it was the last one, setting it’s suffix to “,” if it wasn’t, to “” if it was. Then my template loop was like:March 7th, 2012 at 12:35 am
The template got me most of the way there and I just ended up writing a post processor to remove the excess characters. From the code, it looks like I’d use the “prefix” property of a doctreeargument instead of the suffix. The suffix appears to always return a null.
I’ve found a couple new uses for the doc template in the last week. I wonder how hard it would be to use this to generate SWIG bindings. An exercise left for the reader…
Thanks, Mike!
March 7th, 2012 at 8:47 am
I have an effort in the dist_tools project to auto generate IDL bindings from something similar to a C header file. I am currently using it to generate IDL bindings for MAGMA routines (GPU accelerated LAPACK).