From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: fvdp@decis.be
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Suggestion for Int32.rotate
Date: Thu, 7 Feb 2002 02:07:35 +0100 [thread overview]
Message-ID: <20020207020735.A577@ice.gerd-stolpmann.de> (raw)
In-Reply-To: <3C61958D.C03D2463@decis.be>; from fvdp@decis.be on Wed, Feb 06, 2002 at 21:43:57 +0100
On 2002.02.06 21:43 Frederic van der Plancke wrote:
> Daniel de Rauglaudre wrote:
> >
> > Hi,
> >
> > On Wed, Feb 06, 2002 at 07:01:51PM +0100, Xavier Leroy wrote:
> >
> > > A C-style syntax would be 12345L for int32 and 123456789LL for
> > > int64; what about nativeint? 12345N ? Anything nicer?
> >
>
> A small problem of 12345L is that "L" for "long" is not justified on
> 64-bit platforms, and more importantly it is not at all obvious what
> length it actually represents.
>
> What about 12345i32, 123456789i64, like some C(++) compilers do; that would
> preserve extensibility (in case one wants 123456789i128 in the future),
> and makes the value types clearer and more consistent,
> even though it makes the actual values somewhat less readable, specially
> if one uses an uppercase I. ('N' or (why not) 'L' could be used instead.)
> For native ints we could then chose either 12345i or 12345n. And keep
> the other one for arbitrary-sized integers.
Why not allow "_" in integer literals, so one can write
12345_i32, 123456789_i64, 123_456_789_i64, 123456789_nat,
123456789_big (for bigints). I think this kind of suffix is easier
to remember than a single letter.
Gerd
--
----------------------------------------------------------------------------
Gerd Stolpmann Telefon: +49 6151 997705 (privat)
Viktoriastr. 45
64293 Darmstadt EMail: gerd@gerd-stolpmann.de
Germany
----------------------------------------------------------------------------
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2002-02-07 1:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 23:06 Berke Durak
2002-02-06 18:01 ` Xavier Leroy
2002-02-06 20:08 ` Daniel de Rauglaudre
2002-02-06 20:43 ` Frederic van der Plancke
2002-02-06 22:40 ` Chris Hecker
2002-02-07 1:07 ` Gerd Stolpmann [this message]
2002-02-07 3:05 ` Brian Rogoff
2002-02-07 3:25 ` Eric C. Cooper
2002-02-07 13:49 ` Thorsten Ohl
2002-02-07 13:55 ` Remi VANICAT
2002-02-07 16:32 ` [Caml-list] More syntax: _ in numbers, backquote infix op's Christian Lindig
2002-02-06 21:02 ` [Caml-list] integer types and their literals james woodyatt
2002-02-06 21:36 ` [Caml-list] Suggestion for Int32.rotate Berke Durak
2002-02-07 1:15 ` Gerd Stolpmann
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=20020207020735.A577@ice.gerd-stolpmann.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@pauillac.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