From: Chris Hecker <checker@d6.com>
To: fvdp@decis.be, caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Suggestion for Int32.rotate
Date: Wed, 06 Feb 2002 14:40:17 -0800 [thread overview]
Message-ID: <4.3.2.7.2.20020206143609.00db7ee0@arda.pair.com> (raw)
In-Reply-To: <3C61958D.C03D2463@decis.be>
>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.
I agree with this. Better to give absolute bit lengths in the syntax than to make more abbreviations. But yes, 1234i32 is unreadable. 1234n32 is better. 1234N32 is okay as well.
>Just my €0.02 worth of suggestions... I can live with L and LL.
Same here about L and LL (worth $0.0173425 at today's rate).
Chris
-------------------
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-06 22:40 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 [this message]
2002-02-07 1:07 ` Gerd Stolpmann
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=4.3.2.7.2.20020206143609.00db7ee0@arda.pair.com \
--to=checker@d6.com \
--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