caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Shawn Wagner <shawnw@speakeasy.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml 3.05 released
Date: Mon, 29 Jul 2002 17:46:55 -0700	[thread overview]
Message-ID: <20020729174655.E21999@speakeasy.org> (raw)
In-Reply-To: <20020729144527.A30919@pauillac.inria.fr>; from xavier.leroy@inria.fr on Mon, Jul 29, 2002 at 02:45:27PM +0200

On Mon, Jul 29, 2002 at 02:45:27PM +0200, Xavier Leroy wrote:
> 
> Objective Caml 3.05:
> --------------------
> 
> Language features:
> - Support for polymorphic methods and record fields.
> - Allows _ separators in integer and float literals, e.g. 1_000_000.

Something I've been wanting for a while (And vaguely remember being
discussed on the list a while back) is being able to have literal int32 and
int64 and nativeint values in source files. For example, I have code that
has int32 constants that are too large to fit in a normal caml int, so I'm
stuck doing things like let some_value = Int32.of_string "123456789" at the
moment, which seems icky. For some reason, I was under the impression that
this was going to be in .05. Any chance of it for .06?

> - Unix:
>     use reentrant functions for gethostbyname and gethostbyaddr when available;

Nifty. In a vaguely related note, I'm working off and on on adding support
for IPv6 sockets to the Unix library. I think I just need to finish the
interface code for the C getnameinfo() and getaddrinfo() functions, and do a
merge with the 05 code instead of 04. Is there any interest in making this
part of a future release?

-- 
Shawn Wagner
shawnw@speakeasy.org
-------------------
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


  parent reply	other threads:[~2002-07-30  0:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 12:45 Xavier Leroy
2002-07-29 14:36 ` Nicolas Cannasse
2002-07-30  0:46 ` Shawn Wagner [this message]
2002-07-30  3:50 ` Scott J.
2002-07-30  7:34   ` John Prevost
2002-07-30  7:46   ` [Caml-list] Serious typechecking error involving new polymorphism (crash) John Prevost
2002-07-30  7:58     ` Xavier Leroy
2002-07-30  8:22       ` John Prevost
2002-07-30  8:47         ` Xavier Leroy
2002-07-30  8:37       ` Sven LUTHER
2002-07-30 14:11         ` [Caml-list] bug-fix branches Xavier Leroy
2002-07-30 16:15           ` Sven LUTHER
2002-08-01  9:37           ` [Caml-list] 3.05 and future 3.06 binary compatibility ? root
2002-08-01 12:09             ` [Caml-list] " Xavier Leroy
2002-08-01 15:56               ` Sven LUTHER
2002-08-08  8:37               ` Sven LUTHER
2002-08-09 12:25                 ` Xavier Leroy
2002-08-09 13:16                   ` Sven LUTHER
2002-07-30  7:51   ` [Caml-list] OCaml 3.05 released Dmitry Bely
2002-07-30 15:01     ` Scott J.
2002-07-30 15:11       ` Dmitry Bely
2002-08-02  5:31   ` Jacques Garrigue
2002-08-02 11:15     ` Tim Freeman
2002-07-30  7:48 ` [Caml-list] Record with one non mutable filed Christophe Raffalli
2002-07-30 11:49 ` [Caml-list] OCaml 3.05 released Yaron M. Minsky

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=20020729174655.E21999@speakeasy.org \
    --to=shawnw@speakeasy.org \
    --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).