From: av1474@comtv.ru
To: Damien Doligez <damien.doligez@inria.fr>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 4.02.1 is coming soon
Date: Tue, 23 Sep 2014 20:08:49 +0400 [thread overview]
Message-ID: <87r3z2720e.fsf@comtv.ru> (raw)
In-Reply-To: <F803570D-74BC-4488-8ECE-A01E6BF8D365@inria.fr> (Damien Doligez's message of "Tue, 23 Sep 2014 12:02:15 +0200")
Damien Doligez <damien.doligez@inria.fr> writes:
> Dear OCaml users,
>
> The rather large amount of changes in the newly released 4.02
> inevitably caused some issues in the very first minor release. We
> shall have a 4.02.1 bugfix release coming soon, hopefully in early
> October.
>
> Among the few issues that have now been fixed, there are a few
> regressions in the new, type-safe format implementation
> (Printf/Scanf/Format) -- for advanced formatting features.
>
> There was also a regression in the *compilation time* of the
> distributed OCaml compiler, which is sensibly slower than 4.01 on
> multi-module programs. This is already fixed in the development
> version of the compiler and will be part of the bugfix release.
>
Compilation of [1] skyrocketed (at least here on rather oldish PPC
machine), hopfully things would be a bit better in 4.02.1.
> Any additional testing to find and report other regressions is more
> than welcome. If you have not yet tested your programs with 4.02, now
> is the time to give it a try!
>
>
> -- Damien
[1] http://repo.or.cz/w/llpp.git/blob/53f1bca0140d03d9f2e1437a4ad0dbc3f7e85ce0:/main.ml
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2014-09-23 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPFanBGFts+56d6riBGK+Cj5JhjEpUiabfSUF3MXUQ+8jVdHdQ@mail.gmail.com>
2014-09-23 10:02 ` Damien Doligez
2014-09-23 16:08 ` av1474 [this message]
2014-09-25 3:50 ` Nick Lucaroni
2014-09-25 3:58 ` Nick Lucaroni
2014-09-25 5:11 ` Gabriel Scherer
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=87r3z2720e.fsf@comtv.ru \
--to=av1474@comtv.ru \
--cc=caml-list@inria.fr \
--cc=damien.doligez@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