caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Mr. Herr" <misterherr@freenet.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] is meta-ocaml dead?
Date: Wed, 3 Feb 2016 21:29:22 +0100	[thread overview]
Message-ID: <56B26322.2020602@freenet.de> (raw)
In-Reply-To: <CAJ7XQb4NC5Q6Ecot0Zcp8mxbP+Ksh45cmBnSQJj7raiEHpxAZQ@mail.gmail.com>



On 03.02.2016 21:22, Raoul Duke wrote:
> http://www.cs.rice.edu/~taha/MetaOCaml/
>
> "Download current (February 3nd, 2006)" !!! :-}
>
str@suse132-intel:~> opam switch --all | grep -i meta
--           -- 4.00.1+BER                    BER MetaOCaml
(http://okmij.org/ftp/ML/MetaOCaml.html)
--           -- 4.01.0+BER                    BER-101 MetaOCaml
--           -- 4.02.1+BER                    BER-N102 MetaOCaml

just a quick hint - I did not check what is inside the package.

/Str.

  reply	other threads:[~2016-02-03 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 20:22 Raoul Duke
2016-02-03 20:29 ` Mr. Herr [this message]
2016-02-03 20:34   ` Raoul Duke

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=56B26322.2020602@freenet.de \
    --to=misterherr@freenet.de \
    --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;
as well as URLs for NNTP newsgroup(s).