From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <berenger@riken.jp>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by sympa.inria.fr (Postfix) with ESMTPS id 964E27EEAF
	for <caml-list@sympa.inria.fr>; Fri,  1 Feb 2013 03:13:04 +0100 (CET)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  berenger@riken.jp) identity=pra; client-ip=134.160.33.162;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible
Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of
  berenger@riken.jp designates 134.160.33.162 as permitted
  sender) identity=mailfrom; client-ip=134.160.33.162;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible;
  x-record-type="v=spf1"
Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of
  postmaster@postman.riken.jp designates 134.160.33.162 as
  permitted sender) identity=helo; client-ip=134.160.33.162;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="postmaster@postman.riken.jp";
  x-conformance=sidf_compatible; x-record-type="v=spf1"
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsBAMgiC1GGoCGimWdsb2JhbABFv0sOAQEBAQEGDQsHFCeCHgEBBThAEQsYCRYPCQMCAQIBRRMGAgEBFod3wiCNY4MpA4hijTCFbo1o
X-IPAS-Result: AhsBAMgiC1GGoCGimWdsb2JhbABFv0sOAQEBAQEGDQsHFCeCHgEBBThAEQsYCRYPCQMCAQIBRRMGAgEBFod3wiCNY4MpA4hijTCFbo1o
X-IronPort-AV: E=Sophos;i="4.84,579,1355094000"; 
   d="scan'208";a="700649"
Received: from postman2.riken.jp (HELO postman.riken.jp) ([134.160.33.162])
  by mail3-smtp-sop.national.inria.fr with ESMTP; 01 Feb 2013 03:10:53 +0100
Received: from postman.riken.jp (postman2.riken.jp [127.0.0.1])
	by postman.riken.jp (Postfix) with SMTP id 6D48C12602D3
	for <caml-list@inria.fr>; Fri,  1 Feb 2013 11:12:44 +0900 (JST)
Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98])
	by postman.riken.jp (Postfix) with ESMTPA id D9C881270051
	for <caml-list@inria.fr>; Fri,  1 Feb 2013 11:12:43 +0900 (JST)
Message-ID: <510B249B.5060108@riken.jp>
Date: Fri, 01 Feb 2013 11:12:43 +0900
From: Francois Berenger <berenger@riken.jp>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: caml-list@inria.fr
References: <20130131074903.16892.qmail@www1.g3.pair.com>
In-Reply-To: <20130131074903.16892.qmail@www1.g3.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.1.20322
Subject: Re: [Caml-list] ANN: Brand-new BER MetaOCaml for OCaml 4.00.1

Hello,

Could it be (ab)used to translate easily a whole program's OCaml source
into C code?
I have no need for this right now but I'm just curious.

I wonder if it would be one way to obtain optimized binaries
on architectures for which there is no optimizing compiler.

Regards,
F.

On 01/31/2013 04:49 PM, oleg@okmij.org wrote:
> BER MetaOCaml N100 is now available. It is a strict superset of OCaml
> 4.00.1, extending it with staging annotations to construct and run
> typed code values. BER MetaOCaml has been completely re-implemented
> and thus caught up with OCaml. For those who don't know what staging
> or MetaOCaml is, a short introduction follows the news summary.
 > [...]