caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: Thorsten Ohl <ohl@hep.tu-darmstadt.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] CDK binary release
Date: Fri, 11 May 2001 00:53:45 +0200	[thread overview]
Message-ID: <20010511005345.A13888@miss.wu-wien.ac.at> (raw)
In-Reply-To: <15098.48364.427110.543643@heplix4.ikp.physik.tu-darmstadt.de>; from ohl@hep.tu-darmstadt.de on Thu, May 10, 2001 at 18:08:12 +0200

Thorsten Ohl schrieb am Thursday, den 10. May 2001:
> Yes, but it would be very useful if the markup could serve both purposes
> simultaneously.  I'm using ocamlweb extensively and I find myself
> writing *.mli files that could be turned into online documentation

The same is true for me: the documentation of interfaces is the same
for users of some module and for developers. Only the latter usually
also want to see the documentation of the implementation. Being able
to generate both kinds of documentations without having to write extra
annotations would be a big help! That's why I am a bit reluctant about
cdk_doc, because it only addresses the library user's point of view.

Ocamlweb could probably (please correct me if I am wrong) be turned into
a general tool much more easily than the other approaches I have seen.

Any chance that it (or something similar) could ever get the status of
a standard tool (which cdk_doc seems to be targeting)?

Best regards,
Markus Mottl

-- 
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


  reply	other threads:[~2001-05-10 22:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-07  9:06 Fabrice Le Fessant
2001-05-07 16:09 ` Miles Egan
2001-05-07 17:17 ` John Max Skaller
2001-05-09 10:58 ` Markus Mottl
2001-05-09 12:01   ` [Caml-list] About documentation tools David Mentre
2001-05-09 13:18     ` [Caml-list] " Markus Mottl
2001-05-09 18:17       ` John Max Skaller
2001-05-09 17:58   ` [Caml-list] CDK binary release John Max Skaller
2001-05-09 22:40     ` Markus Mottl
2001-05-09 23:19       ` John Max Skaller
2001-05-10  9:19         ` Fabrice Le Fessant
2001-05-10 10:34           ` [Caml-list] CDK Documentation format Dave Mason
2001-05-13 21:26             ` Stefan Monnier
2001-05-10 11:16           ` [Caml-list] CDK binary release Sven LUTHER
2001-05-10 13:18             ` Markus Mottl
2001-05-10 15:42               ` Jean-Christophe Filliatre
2001-05-10 16:08                 ` Thorsten Ohl
2001-05-10 22:53                   ` Markus Mottl [this message]
2001-05-10 20:36                 ` John Max Skaller
2001-05-10 14:01             ` David Mentre
2001-05-10 15:09             ` Patrick M Doane
2001-05-10 15:06           ` Patrick M Doane
2001-05-11 11:58             ` Fabrice Le Fessant
2001-05-11 15:31               ` John Max Skaller
2001-05-11 15:44                 ` Fabrice Le Fessant
2001-05-13 21:33                 ` Stefan Monnier
2001-05-11 17:30               ` Patrick M Doane
2001-05-12  7:46                 ` Fabrice Le Fessant
2001-05-11 23:24               ` Brian Rogoff
2001-05-10 15:49           ` John Max Skaller
2001-05-14  8:21 ` Olivier Andrieu

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=20010511005345.A13888@miss.wu-wien.ac.at \
    --to=mottl@miss.wu-wien.ac.at \
    --cc=caml-list@inria.fr \
    --cc=ohl@hep.tu-darmstadt.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).