Back-end for Igor Pro code?
Florin <[email protected]>
| Newsgroups | gmane.text.doxygen.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello everybody! I'd like to use doxygen to generate documentation from scripting code for the Igor Pro data analysis tool (http://www.wavemetrics.com/). I put a sample Igor Pro file at http://www.physik.uni-wuerzburg.de/~bflorin/00Nuber.ipf so you can get an impression about how Igor Pro scripting code looks like. The sample code at the URL above has comments which use doxygen-like keywords to emphasize parameters, function briefs etc because I originally intended to write some python scripts to do some very rudimentary parsing & doc generating, but then I figured than since doxygen does such a good job in generating all kinds of documentation outputs, it might be a good idea to somehow teach doxygen how to read Igor Pro files (.IPF) instead of re-inventing the wheel by writing a code documentation program from scratch. So, my question is, what would be the best approach to teach doxygen how to read .IPF files? Where should I start? About my skills: I have quite a lot of experience with like C/C++ and some rudimentary experience with python. I'm average on using regular expressions (mostly gained through shell scripting and sed parsing)... best regards, florin. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/