From: Alain.Frisch@ens.fr
To: "Yaron M. Minsky" <yminsky@cs.cornell.edu>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Big_int comparisons
Date: Mon, 2 Feb 2004 14:36:16 +0100 (MET) [thread overview]
Message-ID: <Pine.SOL.4.44.0402021431580.5376-100000@clipper.ens.fr> (raw)
In-Reply-To: <1075725268.29371.16.camel@flapdragon.homeip.net>
On Mon, 2 Feb 2004, Yaron M. Minsky wrote:
> This confuses me, because as I mentioned, michel quercia appears to have
> fixed this problem while working on Numerix. Here's his patch:
The patch solves the problem for the nat type, not for big_int.
If you know the ordering won't be the natural one for big_int, it is ok,
but this might be confusing, and for this reason Xavier Leroy rejected a
similar patch I proposed.
If you read french:
http://caml.inria.fr/bin/caml-bugs/wish%20not%20granted?id=1445
Note the problem is only for comparison, not for hashing.
> > A solution could be to allow attaching custom generic operations to
> > non-custom blocks (for instance, by boxing values in a block with a
> > special GC tag + the custom operations; i.e.: custom blocks whose content
> > is traced by the GC). This could be implemented with custom blocks by
> > registering/unregistering global roots, but I guess the performance would
> > be bad.
>
> Is that what Michel did?
No.
-- Alain
-------------------
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-02-02 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 19:42 Yaron M. Minsky
2004-02-02 12:23 ` Alain.Frisch
2004-02-02 12:34 ` Yaron M. Minsky
2004-02-02 13:36 ` Alain.Frisch [this message]
2004-02-03 9:52 ` skaller
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=Pine.SOL.4.44.0402021431580.5376-100000@clipper.ens.fr \
--to=alain.frisch@ens.fr \
--cc=caml-list@inria.fr \
--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).