Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Kenneth Knowles <kknowles@berkeley.edu>
To: "William D. Neumann" <wneumann@cs.unm.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANNOUNCE] ocamlconf-0.5 release
Date: Wed, 12 May 2004 14:51:56 -0700	[thread overview]
Message-ID: <20040512215156.GA8592@tallman.kefka.frap.net> (raw)
In-Reply-To: <Pine.LNX.4.56.0405121252530.5791@lascruces.cs.unm.edu>

On Wed, May 12, 2004 at 02:20:20PM -0600, William D. Neumann wrote:
> This is really, I suppose, the heart of my complaint.  It seems that a
> number of OCaml developers are relying on ocamldoc as their primary
> documentation method.  While this may work more-or-less well for a library
> like mlgmp or similar, it is woefully inadequate for documenting anything
> more substantial (e.g. applications).

I basically think of OCamlConf as a library, but agree that ocamldoc output is
not appropriate for applications.  Every time I sit down to write a user's
manual for ocamlconf (It is on the gameplan!) I end up re-hashing the inline
comments almost word-for-word.  I'm not sure the best way to write a tutorial
that is heavily hyperlinked into the code, so it just gives a friendly front-end
to the API.  I'll take a look at ocamlweb; I'm curious about literate programming
but usually find that the ordering necessary in prose is inconvenient for code.

Kenn

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      parent reply	other threads:[~2004-05-12 21:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12  9:59 Kenneth Knowles
     [not found] ` <Pine.LNX.4.56.0405121049030.5791@lascruces.cs.unm.edu>
2004-05-12 18:35   ` Kenneth Knowles
     [not found]     ` <Pine.LNX.4.56.0405121252530.5791@lascruces.cs.unm.edu>
2004-05-12 21:51       ` Kenneth Knowles [this message]

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=20040512215156.GA8592@tallman.kefka.frap.net \
    --to=kknowles@berkeley.edu \
    --cc=caml-list@inria.fr \
    --cc=wneumann@cs.unm.edu \
    /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