Re: [Doxygen-develop] Re: Support for other languages

[Dimitri v. H. <di...@st...>]

On Sun, Dec 26, 2004 at 10:52:24AM -0800, Vicki Brown wrote:
> 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?

Difficult. Imagine that in the filtered code a function call is found
at line x, column y. Then for the unfiltered Python code I would need to
know the corresponding location (x',y'), at which the function is definition 
in the Python source is present in order to make a link (and cross-reference 
with the documentation). How can doxygen compute this if it does not 
understand the unfiltered code? A function call is one example, but the 
same holds for function body start and end, location of a class definition, 
etc, etc. 

So this would only work if either the filter is very simple
(think of simple word replacements), or if both scanner.l and code.l are
rewritten/extended so they understand Python.

Regards,
  Dimitri