From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] CVS tracking and 3.08 testing
Date: Thu, 1 Jul 2004 17:40:11 +0200 [thread overview]
Message-ID: <20040701154011.GA1906@yquem.inria.fr> (raw)
In-Reply-To: <1088691132.2582.137.camel@pelican.wigram>
> OK, any hints on what things to look for?
> Expected problem areas, performance changes,
> cute new features, etc?
The change log (file "ocaml/Changes" in the CVS sources) is relatively
up-to-date. Perhaps the biggest (internal) change is in the
representation of objects and compilation of classes, so if you have
object-heavy programs, that would be a good test.
- Xavier Leroy
-------------------
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:[~2004-07-01 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 13:41 Xavier Leroy
2004-07-01 14:12 ` skaller
2004-07-01 15:40 ` Xavier Leroy [this message]
2004-07-09 18:14 ` Benjamin Geer
2004-07-01 16:58 ` Markus Mottl
2004-07-07 23:51 ` 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=20040701154011.GA1906@yquem.inria.fr \
--to=xavier.leroy@inria.fr \
--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