From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: John Prevost <j.prevost@cs.cmu.edu>, Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Serious typechecking error involving new polymorphism (crash)
Date: Tue, 30 Jul 2002 10:37:51 +0200 [thread overview]
Message-ID: <20020730083751.GA1041@iliana> (raw)
In-Reply-To: <20020730095833.B6564@pauillac.inria.fr>
On Tue, Jul 30, 2002 at 09:58:33AM +0200, Xavier Leroy wrote:
> > I've discovered a fairly serious typechecking bug in 3.05. I'm
> > reporting it on the webpage, but also want to mention it here so that
> > people are aware.
>
> Yes, this is a serious bug with polymorphic methods and fields.
> Expect a 3.06 release as soon as it is fixed. In the meantime, you're
> welcome to experiment with polymorphic methods and fields, but don't
> bet the farm on them...
Xavier, don't you think it would be a good time for going with a dual cvs
branch scheme or something like that, where you have a released branch
(3.05, and bugfix releases : 3.05.1, 3.05.2, etc) and a development
branch (which will become 3.06).
I suppose it is easy now to do a 3.06 bufix release, but what will
happen when you encouter such a serious bug which needs fixing, when you
are in the middle of developpment of the next version, and the cvs tree
is not really in a releasable state ?
In this case, will you revert all your changes and reapply after having
released the bugfix version, hurry the developpment so you can ship the
new version fixing the bug, or just let the bug stay until the next
version is released ?
None of these solutions appear satisfactory.
Friendly,
Sven Luther
-------------------
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
next prev parent reply other threads:[~2002-07-30 8:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 12:45 [Caml-list] OCaml 3.05 released Xavier Leroy
2002-07-29 14:36 ` Nicolas Cannasse
2002-07-30 0:46 ` Shawn Wagner
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 [this message]
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=20020730083751.GA1041@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=j.prevost@cs.cmu.edu \
--cc=xavier.leroy@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).