Wow! No takers to this question? A bit ironic since Sphinx is a tool intended to help make documentation simpler.
Still, it seems that to implement an autodoc capabilityfor SPEC macro source code files, I can add a similar directive (spec:macrofile) to the custom domain, construct a parser for the SPEC macro language, and then build the ReST page(s) in the directive's handler, a sphinx.directives.ObjectDescription object, from analysis of the parser's findings. The code in the autodoc support is the best example of the algorithm simply because it is the only example to date. Any advice? On Friday, June 15, 2012 6:02:56 PM UTC-5, Pete wrote: > > I'm writing a custom domain (specdomain) to support the SPEC macro > language used to operate X-ray diffractometers. Already, there are working > directives and roles for the language primitives. How do I create the > support code for autodoc to extract docstrings and "#:" documentation tags > from the SPEC source source (text) files? Is there an example to follow? > -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To view this discussion on the web visit https://groups.google.com/d/msg/sphinx-dev/-/l6FVdTW-dHEJ. 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.
