From: David Allsopp <dra-news@metastack.com>
To: caml users <caml-list@inria.fr>
Subject: RE: [Caml-list] OCaml 4.06.0+rc1
Date: Mon, 30 Oct 2017 18:25:21 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9016D585CCD@Remus.metastack.local> (raw)
In-Reply-To: <CAPFanBFyc0aZNXY9mwP5Bv71YLt+hsCPUZTCbSO_XhFJA6+Q=w@mail.gmail.com>
Gabriel Scherer wrote:
> Dear OCaml users,
>
> We have created a first release candidate of the upcoming OCaml 4.06.0
> release for your repeated testing pleasure. It is available as opam
> switches 4.06.0.+rc1 (or +rc1+flambda, etc.)
>
> opam switch 4.06.0+rc1
>
> or as source archives at
>
> http://caml.inria.fr/pub/distrib/ocaml-4.06/
>
> The Changelog since 4.05.0 is available at
>
> http://caml.inria.fr/pub/distrib/ocaml-
> 4.06/notes/Changes.4.06.0+rc1.txt
One of the big changes for the native Windows ports of OCaml is that we now have support for UTF-8 filenames in the runtime.
TL;DR functions like Sys.readdir no longer return garbage (or at best locale-specific strings).
I wrote up a post about the details of this large patch at http://www.dra27.uk/blog/platform/2017/10/30/ocaml-unicode.html, which also includes details on compiling OCaml on Windows, as the instructions have altered slightly with 4.06.0.
Some of the fruits of this labour can be seen in our Camel and Cyrillic-laden AppVeyor logs, for example https://ci.appveyor.com/project/avsm/ocaml/build/1.0.4836
Happy Ĥǻḉḱḯṋḡ!
David
next prev parent reply other threads:[~2017-10-30 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 11:49 Gabriel Scherer
2017-10-30 18:25 ` David Allsopp [this message]
[not found] ` <09738422-5ADF-43DE-856A-2727515BD2FA@acm.org>
2017-11-02 11:59 ` David Allsopp
2017-11-03 10:53 ` [Caml-list] Upcoming breaking changes in Ocamldoc 4.06 octachron
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=E51C5B015DBD1348A1D85763337FB6D9016D585CCD@Remus.metastack.local \
--to=dra-news@metastack.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).