From: Jae-Youn Chung <jay@compiler.kaist.ac.kr>
To: Vincent Poirriez <poirriez@univ-valenciennes.fr>
Cc: caml-list@inria.fr
Subject: Re: documentation automatique
Date: 28 Aug 1998 11:59:55 +0900 [thread overview]
Message-ID: <yf4zpcp3j6c.fsf@ruby.kaist.ac.kr> (raw)
In-Reply-To: Vincent Poirriez's message of "Thu, 27 Aug 1998 14:39:32 +0200"
* Vincent Poirriez <poirriez@univ-valenciennes.fr>, 8/27/1998 - 14:39
| I am just reading the new html manual for ocaml 2.0. I appreciate the
| introduction of colours in ocaml presentation.
let me just ask for a favor of me to html version of manual
distributors. I believe that emacs with caml mode and html manual is
a perfect combination for programming in caml.
In many cases, I really miss for the tools like HyperSpec in common
lisp community provided from Harlequin which can be browsed directly
from emacs with small pieces of codes (called hyperspec.el).
This is possible because HyperSpec html document has
<a name="blablah"> xx</a> every identifiers so that we can easily
extract that attributes and write down small elisp code with
browse-url feature.
I've tried to extract every function and type and exceptions in O'caml
manual by observing the patterns but which is not so accurate and in
some cases failed :(.
I think html version must been made from latex or something like
that version. Can anybody add some <a name=XXX> identifiers </a> tag
during the translations so that emacs users can easily adopt it to
his/her tastes?
And one more:
In common lisp, there's nice manual browsing program, not to mention
HyperSpec which is really an good job, something like clman which is
unix *man* like interfaces for lisp functions.
I believe caml manual can easily convert like that way.
| It should be nice if an automatic documentation tool could be provided
| for ocaml. It should take .ml and/or .mli files correctly documented
| and return a nice latex/html (eventually via HeVeA) docummentation.
I don't know what you exactly want, but if you want to convert your
caml code to html with syntax coloring and the like, I'd suggest you
the htmlize.el in emacs which is written by Hrvoje Niksic <hniksic@srce.hr>.
I believe that converting to latex format is not so hard anyway.
(Isn't there many packages which converts program code to latex file?)
--
Chung jay youn
mailto:jay@pllab.kaist.ac.kr
http://pllab.kaist.ac.kr/~jay
next prev parent reply other threads:[~1998-08-29 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-27 12:39 Vincent Poirriez
1998-08-28 2:59 ` Jae-Youn Chung [this message]
1998-08-29 20:36 ` Adam P. Jenkins
1998-08-31 12:48 ` Jan Skibinski
1998-08-31 6:47 ` Francois Pessaux
1998-08-31 12:48 Sven
1998-09-01 9:11 ` Fabrice Le Fessant
1998-08-31 14:36 Ken Wakita
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=yf4zpcp3j6c.fsf@ruby.kaist.ac.kr \
--to=jay@compiler.kaist.ac.kr \
--cc=caml-list@inria.fr \
--cc=poirriez@univ-valenciennes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox