At 10:56 +0100 12/25/2004, Dimitri van Heesch <di...@st...> wrote:
>You can already show the original python sources by setting
>FILTER_SOURCE_FILES to NO. The main problem is that doxygen does not
>understand python so it will not do syntax highlighting and cross-referencing
>properly.
Yes, I _know_ that. That's rather the point.
I want both the cross referencing as well as the Python source.
So I ask again:
If the filters passed along both the translated code and the original
code, Doxygen could use the former for its analysis and the latter for
its code displays. Ideally, this would involve an extension of the
current interface, so that existing filters would still work as they
do now.
How difficult would this be?
> P.S. For Python you could also look at: pydoc, happydoc, or epydoc.
I have looked at them. Doxygen is miles better. Except for the fact that it
makes everything look like C++. Happydoc is... oddly formatted. epydoc
refuses to traverse directory trees. Neither of these seems to understand
source code or cross references very well. I haven't looked at pydoc (my
understanding is that epydoc was written to address lack of functionality in
pydoc and epydoc is lacking in functionality itself).
--
Vicki Brown ZZZ Journeyman Sourceror:
SF Bay Area, CA zz |\ _,,,---,,_ Scripts & Philtres
http://www.cfcl.com zz /,`.-'`' -. ;-;;,_Code, Doc, Process, QA
http://cfcl.com/vlb |,4- ) )-,_. ,\ ( `'-'Perl, Unix, Mac OS X, WWW
____________________ '---''(_/--' `-'\_) ___________________________
|
