-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 26.01.2010 23:14, schrieb Andras Vukics: > Dear All, > > I'd like to use sphinx for documenting a c++ project and reading > through the documentation I encountered a few issues: What would be a > good way to markup and reference c++ namespaces and header files? In > Python a module replaces and unifies these two concepts. Therefore, > the module markup cannot really be used for these c++ concepts, and > also the syntax is different from the Python syntax > module.something_in_the_module . Another thing is that a macro which > takes arguments cannot always be classified as something equivalent to > a function since the macro can stand for a type which takes arguments > (c++ class templates). > > Is there any clever way that I can still use the existing markup and > get around these issues? > Or is there any extension for sphinx that allows for more refined > markup of c++ constructs? > Or do I have to write one myself?
Besides Michael's "breathe", the new domains support in the upcoming Sphinx 1.0 will mean that writing an extension for supporting C++ documentation will be much easier than it is with 0.6. I will probably implement C++ as an example, since it seems to be the one most asked for, and the one with more interesting cases than e.g. JavaScript. The timeframe is something between one and three months. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAktlqmAACgkQN9GcIYhpnLAbQgCdEYIBU/+EB+iVk3aHQO03hZK+ dWoAn1yUmlo5q1QXZTAKUBEnkv2HuuLU =OevN -----END PGP SIGNATURE----- -- 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.
