It is still a work in progress but you might consider looking at breathe which attempts to bridge between sphinx and doxygen. Far from perfect though.
http://github.com/michaeljones/breathe Michael On Wed, Jan 27, 2010 at 1:38 PM, Fred Drake <[email protected]> wrote: > On Tue, Jan 26, 2010 at 5:14 PM, Andras Vukics <[email protected]> > wrote: >> Is there any clever way that I can still use the existing markup and >> get around these issues? > > My own inclination is to avoid cleverness and identify or create > markup that makes sense for the semantics you need to support. C and > C++ have some real differences that shouldn't be papered over too > casually. > >> Or is there any extension for sphinx that allows for more refined >> markup of c++ constructs? > > I don't know if anyone's done any work on this before or not, but even > better markup for the C constructs that occur in Python documentation > (as found in the "Extending & Embedding" and "C API Reference") would > be welcome. > > > -Fred > > -- > Fred L. Drake, Jr. <fdrake at gmail.com> > "Chaos is the score upon which reality is written." --Henry Miller > > -- > You received this message because you are subscribed to the Google Groups > "sphinx-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sphinx-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
