From: Oleg Trott <oleg_trott@columbia.edu>
To: fvdp@decis.be, OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Int overflow in literals
Date: Thu, 30 Oct 2003 18:43:35 -0500 [thread overview]
Message-ID: <200310301843.35157.oleg_trott@columbia.edu> (raw)
In-Reply-To: <3FA18458.6F8F30D5@decis.be>
On Thursday 30 October 2003 04:36 pm, Frederic van der Plancke wrote:
> Issac Trotts wrote:
> > On Thu, Oct 30, 2003 at 02:53:32PM +0100, Marcin 'Qrczak' Kowalczyk 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.
> >
> > If you want to be sure that the number is correctly stored, you can use
> > Int64:
> >
> > Int64.of_string "10000000000"
> >
> > Issac
>
> That was not my problem. My problem was to be able to read a list of
> integers from a file and be warned in case of overflow. And to be able to
> rely on int_of_string for that purpose. I got hit... of course now I know,
> but other innocent programmers may get hit in the future as well. (Not to
> speak of the not-so-innocent people who wrote this nice OCaml compiler ;-)
... and this is what Issac (and myself) suggested (by implication):
let int_of_string s =
Big_int.int_of_big_int (Big_int.big_int_of_string s)
We addressed your specific problem. But I agree with you that it would be
nice to have the safe behavior in OCaml by default (at least for parsing,
where performance wouldn't be affected)
--
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-30 23:44 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 [this message]
2003-10-31 16:42 ` Xavier Leroy
2003-10-31 17:39 ` Marcin 'Qrczak' Kowalczyk
2003-10-31 17:50 ` Oleg Trott
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=200310301843.35157.oleg_trott@columbia.edu \
--to=oleg_trott@columbia.edu \
--cc=caml-list@inria.fr \
--cc=fvdp@decis.be \
/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