From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: christo@nextsolution.co.jp
Cc: caml-light@inria.fr
Subject: Re: O'Caml next release
Date: Tue, 18 Feb 1997 17:23:48 +0100 (MET) [thread overview]
Message-ID: <199702181623.RAA28526@pauillac.inria.fr> (raw)
In-Reply-To: <199702181505.QAA25918@pauillac.inria.fr> from Pierre Weis at "Feb 18, 97 04:05:42 pm"
> In the next release of Objective Caml, will there be changes for objects
> along the lines discussed on the list (more flexible initialization,
> Smalltalk-like method invocation)? Roughly when will the next release become
> available?
I'll let others answer the questions about the object stuff. As for
the next release, I'm planning one at the end of the month or perhaps
in early March. The main visible novelty will be the replay debugger,
which was finally ported from Caml Light, plus an SGI port and a
bunch of small fixes.
Regards,
- Xavier Leroy
next parent reply other threads:[~1997-02-19 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199702181505.QAA25918@pauillac.inria.fr>
1997-02-18 16:23 ` Xavier Leroy [this message]
1997-02-18 17:45 ` Jerome Vouillon
1997-02-17 0:50 Frank Christoph
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=199702181623.RAA28526@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-light@inria.fr \
--cc=christo@nextsolution.co.jp \
/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