C source viewer/mapper?

[Dave Kuhlman]

Simon Burton wrote:

[snip]

I'd like to suggest that your header/interface parser generate XML that 
describes the interface.  If you do that, others can write processors that 
transform the XML for different purposes, generate wrappers, generate 
documentation, perform code analysis, etc.  And, best of all, these tools 
(for transformation, analysis, etc) could be written in Python. By 
generating XML, you are in effect making the output of your parser public.

You may want to look at the following for inspiration:

  - SWIG generates XML if you use the "-xml" option.

  - http://www.mip.sdu.dk/~fonseca/idl/

Dave


> 
> I am working on a c code parser written in python right now.
> My main focus is parsing .h files to generate wrapper code for python
> (yes i know about SWIG), but i hope it will do a lot more, such
> as general "explaining" that you (and many others) would like.
> 
> highlighting external traffic to sockets is somewhat specific,
> but my hope is that a well written python c-parser will allow for
> custom extensions without to much hassle.
> 
> let me know if you're interested; i'll announce something on c.l.py
> soon i hope,
> 
> cheerioh,
> 
> Simon Burton
> http://arrowtheory.com

-- 
Dave Kuhlman
dkuhlman at rexx.com
http://www.rexx.com/~dkuhlman