Hi Paul, You might want to take a look at my proposal for last year GSoC which attempted to provide the same functionality: http://leapon.net/files/Multiple%20language%20support%20for%20autodoc%20in%20Sphinx%20via%20ANTLR.html (since it's from one year ago, excuse me for broken links and outdated information).
Also Michael the creator of Breathe <http://github.com/michaeljones/breathe> emailed me before about the proposal just out of curiosity, and this is my reply: Hi Michael, Sorry but the proposal remained a proposal and has not been implemented :( I don't have plans to do it in the near future either (too busy with school). I've skimmed the docs for Breathe and it seems to be a very nice concept! This is actually quite similar to the project that I wanted to work on the first time. However after discussing at #pocoo, some were not very keen of the idea of using doxygen because doxygen itself is "not good enough" a software overall. A real parser like ANTLR-generated ones are definitely better but implementation would definitely be more difficult since it's lower level. Some after suggested using clang (a production-ready parser-compiler for C-like languages). In any case, you project is better because you have an implementation instead of just a plan :) Nevertheless you are welcome to retrofit/modify/implement the project plan! Then his reply (pardon me for posting this without permission, I hope you don't mind Michael!): Hey, thanks for the information. You're right, there is something less > than desirable about Doxygen, but as you say, it lets you ship > something quicker so I decided to role with that. I aimed to improve > the parser at some point, but really doxygen already does a bunch of > languages and I mainly use C++ and that is meant to be horrible to > parse, so I took to lazy route. [...] -------- Leontius Adhika Pradhana (Leon) http://leapon.net/ On Thu, Feb 17, 2011 at 10:17 PM, daspostloch <daspostl...@googlemail.com>wrote: > Hi all, > > Having installed Sphinx only some days ago, I quickly > had a look into the Doxygen/XML bridge Breathe [1] > written by Micheal Jones. I found the idea very neat. > > Sphinx has become one of the de-facto standards for > python documentation, and it seems plausible that it > would have major impact on, e.g., the C++ world as well, > provided that the technology is available. However, > Micheal has said in a post that he plans to start > ceasing further Breathe development. > > Having noted this, I wanted to ask if there are any > Sphinx plans for the 2011 Google Summer of Code, and > if so, maybe suggest to check if some Breathe targets > could be included before the fast approaching deadline? > > If yes, this important bridge to other programming > languages could be fostered further. As a side note, > I have also been pointed to the doxylink project [2], > which seems to be a good intermediate workaround. Or > does the Sphinx community feel this way of linking to > a third system would be the desired solution permanently? > > Cheers, Paul > > > [1] http://michaeljones.github.com/breathe/ > [2] http://packages.python.org/sphinxcontrib-doxylink/index.html > > -- > You received this message because you are subscribed to the Google Groups > "sphinx-dev" group. > To post to this group, send email to sphinx-dev@googlegroups.com. > To unsubscribe from this group, send email to > sphinx-dev+unsubscr...@googlegroups.com. > 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 sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
