From: skaller <skaller@users.sourceforge.net>
To: yminsky@cs.cornell.edu
Cc: Markus Mottl <markus@oefai.at>,
Jean-Christophe Filliatre <jean-christophe.filliatre@lri.fr>,
Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Counting bits in a big_int
Date: 16 May 2004 10:51:20 +1000 [thread overview]
Message-ID: <1084668678.19838.44.camel@pelican.wigram> (raw)
In-Reply-To: <891bd339040515131939afd837@mail.gmail.com>
On Sun, 2004-05-16 at 06:19, Yaron Minsky wrote:
> Nice. The weird thing about the Nat module is that it's completely
> undocumented. Is there any reason to think it wil be stable between
> revisions?
Yes, the Ocaml people care about that.
> For instance, does Xavier's reimplementation have the same
> Num module with the same interface as the previous one?
Yes. I've been using Nat for ages and had no problems
with upgrades.
> I guess my real question is: why is Nat undocumented?
Documentation requires work, its fairly easy to guess
what Nat does from the function names .. :)
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
-------------------
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
next prev parent reply other threads:[~2004-05-16 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 3:22 Yaron Minsky
2004-05-12 4:19 ` Michael Hoisie
[not found] ` <16547.8441.559944.112854@gargle.gargle.HOWL>
[not found] ` <891bd3390405130427180c36d6@mail.gmail.com>
[not found] ` <16547.27869.60461.270873@gargle.gargle.HOWL>
2004-05-15 2:53 ` Yaron Minsky
2004-05-15 11:14 ` Markus Mottl
2004-05-15 20:19 ` Yaron Minsky
2004-05-16 0:51 ` skaller [this message]
2004-05-16 7:30 ` Xavier Leroy
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=1084668678.19838.44.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=jean-christophe.filliatre@lri.fr \
--cc=markus@oefai.at \
--cc=yminsky@cs.cornell.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;
as well as URLs for NNTP newsgroup(s).