From: Pierre Weis <pierre.weis@inria.fr>
To: xavier.leroy@inria.fr (Xavier Leroy)
Cc: jscott@planetinternet.be, caml-list@inria.fr
Subject: Re: [Caml-list] Runtime overflow and what to do
Date: Sun, 13 Oct 2002 12:19:07 +0200 (MET DST) [thread overview]
Message-ID: <200210131019.MAA20723@pauillac.inria.fr> (raw)
In-Reply-To: <20021013112537.J13771@pauillac.inria.fr> from Xavier Leroy at "Oct 13, 102 11:25:37 am"
> > So it is not easy, perhaps even impossible if the processor doesn't set a
> > flag .
>
> It is possible, but slow and not pretty!
I must precise that even if the code to implement arithmetics with
overflow checks can be considered as ``not pretty'', its usage is
absolutely easy and transparent in Caml: just write a specialized
module for arithmetics with overflow checks (say ``Cautious_arith'')
that redefines ( + ), ( - ), ( * ), ( / ), min, etc, along the lines
sketched by Xavier for addition (by the way, writing such a module is
a very pleasant home exercise); once you have written the
Cautious_arith module, write your application code as usual.
Now, if you want overflow checks just add
open Cautious_arith
at the beginning of your module and recompile.
If you changed your mind, and want to recover the normal speed of
integer arithmetic operations, just remove the open directive and
recompile!
This is an elegant and clean application of very basic operators
redefinition that not so many programming languages offer.
Pierre Weis
INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/
-------------------
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:[~2002-10-13 10:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 15:01 Scott J,
2002-10-10 15:07 ` Maxence Guesdon
2002-10-10 15:11 ` Maxence Guesdon
2002-10-10 15:21 ` Luc Maranget
2002-10-10 18:13 ` Sven LUTHER
2002-10-10 18:57 ` Xavier Leroy
2002-10-10 22:17 ` Scott J,
2002-10-11 8:00 ` Sven LUTHER
2002-10-11 10:16 ` Alessandro Baretta
2002-10-12 16:13 ` John Carr
2002-10-12 16:58 ` Sven LUTHER
2002-10-12 17:12 ` John Prevost
2002-10-13 9:31 ` Xavier Leroy
2002-10-13 9:52 ` Sven LUTHER
2002-10-13 9:57 ` Xavier Leroy
2002-10-13 10:15 ` Sven LUTHER
2002-10-13 13:25 ` John Carr
2002-10-13 9:28 ` Xavier Leroy
2002-10-14 0:56 ` Chris Hecker
2002-10-14 9:46 ` Jacques Garrigue
2002-10-14 11:02 ` Scott J,
2002-10-14 14:05 ` Tim Freeman
2002-10-14 15:32 ` Stefano Zacchiroli
2002-10-14 16:12 ` Alain Frisch
2002-10-14 16:49 ` [Caml-list] new ocaml switches (was Re: Runtime overflow and what to do) Chris Hecker
2002-10-13 9:25 ` [Caml-list] Runtime overflow and what to do Xavier Leroy
2002-10-13 10:04 ` Daniel de Rauglaudre
2002-10-13 10:29 ` Pierre Weis
2002-10-13 10:47 ` Daniel de Rauglaudre
2002-10-13 12:38 ` Pierre Weis
2002-10-13 16:14 ` Xavier Leroy
2002-10-13 17:06 ` Michel Quercia
2002-10-15 19:15 ` Pierre Weis
2002-10-15 19:25 ` Xavier Leroy
2002-10-16 8:24 ` Pierre Weis
2002-10-13 10:19 ` Pierre Weis [this message]
2002-10-11 8:02 ` Sven LUTHER
2002-10-11 6:42 ` Florian Hars
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=200210131019.MAA20723@pauillac.inria.fr \
--to=pierre.weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=jscott@planetinternet.be \
--cc=xavier.leroy@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