Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Lukasz Stafiniak <lukstafi@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCamlDuce 3.08.4
Date: Fri, 26 Aug 2005 02:00:00 +0200	[thread overview]
Message-ID: <4a708d20508251700632c6963@mail.gmail.com> (raw)
In-Reply-To: <1124997485.16161.135.camel@localhost.localdomain>

> On Thu, 2005-08-25 at 20:53 +0200, Alain Frisch wrote:
> > skaller wrote:
> > > Just to confirm please, my understanding is that there is a good
> > > chance OcamlDuce will just become Ocaml (perhaps Ocaml 4.0?)
> >
> > Not at all. Where did you get this impression?
> 
> Don't know .. but then the question .. why not?
> 
What about a notion of supported extensions. These would not be
included into the main distribution, but each of them would have a
branch extending each other, so the user can bake any combination (or
merger) of them.

Best Regards,
Lukasz


  reply	other threads:[~2005-08-26  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 16:53 Alain Frisch
2005-08-25 18:53 ` [Caml-list] " skaller
2005-08-25 18:53   ` Alain Frisch
2005-08-25 19:18     ` skaller
2005-08-26  0:00       ` Lukasz Stafiniak [this message]
2005-08-26 17:05         ` Alain Frisch
2005-08-26 23:21           ` skaller

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=4a708d20508251700632c6963@mail.gmail.com \
    --to=lukstafi@gmail.com \
    --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