Re: [pygccxml-development] C++ wiki like editor using pygccxml

[Roman Y. <rom...@gm...>]

On 8/21/06, rodrigo benenson <rod...@gm...> wrote:
> Thanks for your reply !
> It looks great. Using pygccxml+ doc_extractor I can obtain, for every
> file in the code:
> - All the declarations
> - They exact location in the source code
> - The documentation associated to them
>
> >There are few other: macros and templates
>
> What do you mean ? I presume that GccXml provides your the information post
> Macro parsing, so probably they are not included in the description
> (#define Pi would not appear).

You should ask you self what do your users expects? For example if macro
is used to hide platform differences or to introduce different code in
debug and release
mode. I think, users will prefer to see macro and not the code
generated by macro.
Optionally, you can provide "go down" functionality.

> But templates ? Since you have the declaration of the template class
> of function, which is the actual problem？

GCCXML only dumps template instantiations :-(. The problem with
templates is almost
same as with macros.

> Thanks for pointing out, doxygen. We are in discussions with Doxys (a
> doxygen fork) guys to evaluate a "less on-the-flight" approach.

Good luck

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/