From: Jim Pryor <lists+caml@jimpryor.net>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: How public is Num.Nat
Date: Sat, 10 Jul 2010 10:56:15 -0400 [thread overview]
Message-ID: <20100710145615.GE2772@vaio.earthlink.net> (raw)
In-Reply-To: <20100710124228.GD2772@vaio.earthlink.net>
On Sat, Jul 10, 2010 at 08:42:28AM -0400, Jim Pryor wrote:
> Hi I'm looking into wrapping the Nat module from the Num package. I
> can't find any documentation for it, but the source + a bit of guesswork makes
> it somewhat accessible.
>
> However, superficially at least it looks like this library enables
> arbitrary getting/setting of bytes in the program's heap, with no
> bounds checking. Please tell me it's not so!
I found the documentation from 1992 here:
ftp://ftp.inria.fr/INRIA/publication/publi-pdf/RT/RT-0141.pdf
Not quite the same location listed in Ch 22 of the ref manual, but not
too far off, either. It seems that what I observed is indeed the documented
behavior of the Nat module. The Big_int and Num modules hide that
nastiness away.
--
Jim Pryor
profjim@jimpryor.net
prev parent reply other threads:[~2010-07-10 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 9:33 Andrej Bauer
2010-07-10 12:42 ` Jim Pryor
2010-07-10 14:56 ` Jim Pryor [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=20100710145615.GE2772@vaio.earthlink.net \
--to=lists+caml@jimpryor.net \
--cc=caml-list@yquem.inria.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