From: Oleg Trott <oleg_trott@columbia.edu>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Int overflow in literals
Date: Fri, 31 Oct 2003 12:50:55 -0500 [thread overview]
Message-ID: <200310311250.55112.oleg_trott@columbia.edu> (raw)
In-Reply-To: <20031031174215.A17345@pauillac.inria.fr>
On Friday 31 October 2003 11:42 am, Xavier Leroy wrote:
> > I understand that int overflow is not checked on arithmetic for
> > efficiency reasons, but IMHO it would be better if it was checked
> > at least in literals. When someone writes 10000000000, he certainly
> > does not mean -737418240.
> > It caused confusion in a class when someone was interactively testing
> > a function with larger and larger inputs.
>
> This is a very good suggestion. There are several ways to go about this:
>
> - The lexer emits a warning in case of overflow, and proceeds with
> the value modulo the size of the type.
> - The lexer emits an error on overflow.
> - The int_of_string functions raise an exception on overflow.
>
> Based on the comments posted so far on this list, and on a quick
> discussion with colleagues, I'm inclined toward the third approach
> (int_of_string fails in case of overflow). Does anyone know of a use
> scenario where this new behavior of int_of_string would be a problem?
How much do you think the performance of "typical programs" would be affected
(in percent) if +, - and * were also made to raise an exception on overflow?
--
Oleg Trott <oleg_trott@columbia.edu>
-------------------
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:[~2003-10-31 17:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 13:53 Marcin 'Qrczak' Kowalczyk
2003-10-30 17:37 ` Alex Baretta
2003-10-30 17:59 ` Frederic van der Plancke
2003-10-30 19:20 ` Oleg Trott
2003-10-30 19:40 ` Marcin 'Qrczak' Kowalczyk
2003-10-30 20:05 ` Issac Trotts
2003-10-30 21:14 ` Oleg Trott
2003-10-30 21:26 ` Kenneth Knowles
2003-10-31 0:18 ` Jacques Garrigue
2003-10-31 2:05 ` Kenneth Knowles
2003-11-02 15:05 ` skaller
2003-11-02 16:23 ` Brian Hurt
2003-11-02 16:39 ` Marcin 'Qrczak' Kowalczyk
2003-11-07 7:22 ` skaller
2003-10-30 21:36 ` Frederic van der Plancke
2003-10-30 23:27 ` Issac Trotts
2003-10-30 23:43 ` Oleg Trott
2003-10-31 16:42 ` Xavier Leroy
2003-10-31 17:39 ` Marcin 'Qrczak' Kowalczyk
2003-10-31 17:50 ` Oleg Trott [this message]
2003-11-02 15:23 ` skaller
2003-11-02 16:37 ` Marcin 'Qrczak' Kowalczyk
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=200310311250.55112.oleg_trott@columbia.edu \
--to=oleg_trott@columbia.edu \
--cc=caml-list@inria.fr \
--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