On Tue, Jan 26, 2010 at 5:14 PM, Andras Vukics 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 s
Hi everybody,
thanks for sphinx, first of all. I am creating documentation of yade
simulation software, which has hand-written and autogenerated part
(both sphinx, of course). The auto-generated part documents pure-
python functions/classes and also (many) c++ classes exposed via
boost::python.
C
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 marku
