From: Chris Hecker <checker@d6.com>
To: caml-list@inria.fr
Subject: [Caml-list] int32/int64 literals in next release?
Date: Wed, 13 Nov 2002 14:03:50 -0800 [thread overview]
Message-ID: <200211132203.gADM3nN14766@plinky.bolt-action.com> (raw)
Is there any chance some way of inputing int32/int64 literals can be
added to the compiler for this next release? It's a pain in the rear
to convert them from strings and whatnot, and as they become more and
more usable (unboxing optimizations, used in more apis, work in
printf/scanf, etc.) it becomes relatively more of a pain to initialize
the damn things. And, I'd say it's more likely that you'll use
int32/int64 with constant bit patterns in source because they're
full-width and useful for interfacing with the outside world. It
would also eliminate the need for the really silly part at the top of
the two interfaces with the "chosen constants":
<<
val zero : int32
>>
The 32-bit integer 0.
<<
val one : int32
>>
The 32-bit integer 1.
<<
val minus_one : int32
>>
The 32-bit integer -1.
There have been a bunch of syntax proposals on this list before. I'd
be happy with any of them as long as there was some way to do it (in
hex,dec,bin,oct of course, and with the new _ separator :).
Thanks,
Chris
-------------------
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 reply other threads:[~2002-11-13 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 22:03 Chris Hecker [this message]
2002-11-13 21:42 ` Pierre Weis
2002-11-14 7:44 ` Shawn Wagner
2002-11-14 8:49 ` Yurii A. Rashkovskii
2002-11-15 0:14 ` Shawn Wagner
2002-11-15 5:32 ` Daniel de Rauglaudre
2002-11-26 7:10 ` Shawn Wagner
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=200211132203.gADM3nN14766@plinky.bolt-action.com \
--to=checker@d6.com \
--cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).