4 Responses to “IDLdoc 3.4.3 released”

1. Jim P says:
   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.

2. Michael Galloy says:
   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 a suffix 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:

   [% FOREACH p IN args][% SCOPE p %]...[% suffix %][% END %][% END %]
   

3. Jim P says:
   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!

4. Michael Galloy says:
   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).