From: Nick Lucaroni <nicholas.r.lucaroni@gmail.com>
To: av1474 <av1474@comtv.ru>, caml-list@inria.fr
Cc: Damien Doligez <damien.doligez@inria.fr>
Subject: Re: [Caml-list] OCaml 4.02.1 is coming soon
Date: Wed, 24 Sep 2014 23:58:56 -0400 [thread overview]
Message-ID: <CAADdkeLfvngzuT_+-emaRxyGDE7v-VLXoCwMRs4Es7UaMch7iQ@mail.gmail.com> (raw)
In-Reply-To: <CAADdkeJUt9_h6ujFbaC0LJapUwHwztBRgnP-ntFtsGUW3K55bQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]
I forgot we had been using some magic to convert strings. that's the price
we pay.
nick
On Wed, Sep 24, 2014 at 11:50 PM, Nick Lucaroni <
nicholas.r.lucaroni@gmail.com> wrote:
> Are the formatting issues resolved in the 4.02.0+turnk switch in OPAM
> (that's, dev0-2014-08-29)? I'm getting segmentation faults from fprintf in
> my application even in that branch (see below). I'll work to pin it down as
> it very well could be a miss-formatted string on my part, but obviously we
> shouldn't seg-fault. let me know if I should hold off.
>
> thanks,
> nick
>
> Time: 48706621 - pc: 98976 - module CamlinternalFormat
> 1375 fun k o acc fmt -> <|b|>match fmt with
>
>
>
> On Tue, Sep 23, 2014 at 12:08 PM, <av1474@comtv.ru> wrote:
>
>> 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
>>
>> --
>> Caml-list mailing list. Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>
>
[-- Attachment #2: Type: text/html, Size: 3923 bytes --]
next prev parent reply other threads:[~2014-09-25 3:59 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
2014-09-25 3:50 ` Nick Lucaroni
2014-09-25 3:58 ` Nick Lucaroni [this message]
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=CAADdkeLfvngzuT_+-emaRxyGDE7v-VLXoCwMRs4Es7UaMch7iQ@mail.gmail.com \
--to=nicholas.r.lucaroni@gmail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).