caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Yaron Minsky" <yminsky@cs.cornell.edu>
To: "Damien Doligez" <damien.doligez@inria.fr>
Cc: "caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] release 3.09.2
Date: Fri, 14 Apr 2006 12:13:39 -0400	[thread overview]
Message-ID: <891bd3390604140913q32862620j89cda1291a3aed28@mail.gmail.com> (raw)
In-Reply-To: <B16C0E9E-B566-46A8-A8A0-D09C3285FF07@inria.fr>

[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]

For those of us who have been using 3.09.2+rc1, have there been any
significant bugfixes from that release?

Thanks,
Yaron Minsky

On 4/14/06, Damien Doligez <damien.doligez@inria.fr> wrote:
>
> Hello,
>
> It is our pleasure to announce the availability of OCaml version 3.09.2.
>
> This is mainly a bug-fix release, with only one big new feature: the
> port
> to Mac OS X on Intel processors.
>
> See below for a list of changes with respect to 3.09.1.
>
> It is currently available in source form at
> < http://caml.inria.fr/pub/distrib/ocaml-3.09/ > and it will shortly be
> added to our Web page at < http://caml.inria.fr/ocaml/release.en.html >,
> where binary packages will soon be available.
>
> -- The OCaml team
>
>
> Bug fixes:
> - Makefile: problem with "make world.opt" PR#3954
> - compilers: problem compiling several modules with one command line
> PR#3979
> - compilers,ocamldoc: error message that Emacs cannot parse
> - compilers: crash when printing type error PR#3968
> - compilers: -dtypes wrong for monomorphic type variables PR#3894
> - compilers: wrong warning on optional arguments PR#3980
> - compilers: crash when wrong use of type constructor in let rec PR#3976
> - compilers: better wording of "statement never returns" warning PR#3889
> - runtime: inefficiency of signal handling PR#3990
> - runtime: crashes with I/O in multithread programs PR#3906
> - camlp4: empty file name in error messages PR#3886
> - camlp4: stack overflow PR#3948
> - otherlibs/labltk: ocamlbrowser ignores its command line options
> PR#3961
> - otherlibs/unix: Unix.times wrong under Mac OS X PR#3960
> - otherlibs/unix: wrong doc for execvp and execvpe PR#3973
> - otherlibs/win32unix: random crash in Unix.stat PR#3998
> - stdlib: update_mod not found under Windows PR#3847
> - stdlib: Filename.dirname/basename wrong on Win32 PR#3933
> - stdlib: incomplete documentation of Pervasives.abs PR#3967
> - stdlib: Printf bugs PR#3902, PR#3955
> - tools/checkstack.c: missing include
> - yacc: crash when given argument "-" PR#3956
>
> New features:
> - ported to MacOS X on Intel PR#3985
> - configure: added support for GNU Hurd PR#3991
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> 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: 3202 bytes --]

  reply	other threads:[~2006-04-14 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 13:13 Damien Doligez
2006-04-14 16:13 ` Yaron Minsky [this message]
2006-04-18 12:40   ` [Caml-list] " Damien Doligez
2006-05-10 23:10 ` Binary RPMs for 3.09.2 Aleksey Nogin

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=891bd3390604140913q32862620j89cda1291a3aed28@mail.gmail.com \
    --to=yminsky@cs.cornell.edu \
    --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).