All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Addition of source code documentation generation to the build system?
Date: Mon, 04 Mar 2013 13:57:16 +0100	[thread overview]
Message-ID: <51349A2C.609@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1303041338350.1984@hadrien>

> On the other hand, I'm not sure what the purpose of all of this is.

I hope to achieve a better understanding for your software by the presentation
style from the tool "ocamldoc". (It supports also to generate Graphviz files.)


> If it is only to be able to write ocaml code that processes the C abstract
> syntax tree, then it should be enough to consider the files in the
> parser_c directory.  These are however the ones where there is a risk of a
> missing mli file.

I guess that it is still a configuration challenge to set some variables in a
way so that all dependencies like needed modules can be resolved for the
documentation.

Regards,
Markus

  reply	other threads:[~2013-03-04 12:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 20:21 [Cocci] Addition of source code documentation generation to the build system? SF Markus Elfring
2013-03-04 10:10 ` Julia Lawall
2013-03-04 12:20   ` SF Markus Elfring
2013-03-04 12:42     ` Julia Lawall
2013-03-04 12:57       ` SF Markus Elfring [this message]
2013-03-04 13:09         ` Julia Lawall
2013-03-05  9:20       ` SF Markus Elfring
2013-03-05  9:30         ` Julia Lawall
2013-03-05  9:55           ` SF Markus Elfring
2013-03-05 10:06             ` Julia Lawall
2013-03-05 10:22               ` SF Markus Elfring
2013-03-05 10:28                 ` Julia Lawall
2013-03-05 10:42                   ` SF Markus Elfring
2013-03-05 10:49                     ` Julia Lawall
2013-03-05 13:24                       ` SF Markus Elfring
2013-03-05 16:34                         ` Arie Middelkoop
2013-03-05 17:08                           ` SF Markus Elfring
2013-03-05 20:44                           ` SF Markus Elfring
2013-03-07  9:55                             ` SF Markus Elfring
2013-03-05 16:01                       ` SF Markus Elfring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51349A2C.609@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=cocci@systeme.lip6.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.