>
> I discover also Sphinx and all the toolchains associated as it appears
> AdaCore has dropped TeXINFO for these new Python based tools.
I consider it fairly ridiculous but over the last years AdaCore has become
more of a Python shop than an Ada shop outside the compiler itself.
> The only current Spec -> Doc tool that exists for Ada 2005/2012 is GPS /
>> gnatdoc and I don't like the results nor that it depends on Asis which
>> is generally not available on the FSF compilers.
>>
>
> For my information :
>
> - What is the problem in the outputs of GnatDoc/Sphinx ? (I've only seen
> PDF outputs... good at first glance)
>
I've never seen it work properly to generate full inheritance trees, etc.
If AdaCore was more community oriented I'd probably consider looking at
fixing their code, but I have little interest in Python and as I mentioned
if I am not going to have ASIS available on most platforms I don't want to
use it.
> - I wonder if Ludovic allways maintain ASIS for Gnat in Debian ?
>
It is a very good question. If they have some easy way of maintaining for
Debian that could be transferred to other platforms that may make it more
realistic a tool to use. I've asked the question on CLA, let's see what
comes back.
> I'll look into Gnoga_Doc with interest. It could be fine to be able, in
the future, to mix technical writing (hand write docs) with automatically
generated docs, all that with a pure Ada toolchains.
Since my goal with Gnoga_Doc is to parse out just enough for the
documentation and to produce some intermediate database. I don't see why
that database could not be reused for any purpose desired. You could even
create an application that used tokens of some sort to drop in the
appropriate parsed info where desired in a hand writte doc.
I don't know that I will be the one doing that, but perhaps yourself :)
> ReStructuredText format (I must admit it's simpler than TeXINFO syntax),
Sphinx (looks very powerfull with its html, man, pdf and even LaTeX
outputs... good for formulas.... Maths expressions are handled... this is
mandatory, I think, for technical docs.
I don't see why it wouldn't be possible to take what is parsed and generate
something for TeXINFO or Sphinx or any other format.
> Mixing Gnoga_Doc with this could be a path to dig... I don't know what
you have planned for Gnoga Docs at the whole...
For myself I mainly want the ability to access parsed data from the specs
for the IDE and to produce a maintainable RM from the specs. I think though
a lot more is possible and perhaps I, you or others will consider expanding
on Gnat_Doc and writing various filters tools around the database it
produces.
> (sorry for my english, I'm 'rusted')
Is great, no worries. If people can stand my spelling and absent minded
messages yours are an improvement on them :)
David Botton
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Gnoga-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gnoga-list
