From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id 001B87ED52 for ; Wed, 25 Jul 2012 17:51:42 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of dra-news@metastack.com) identity=pra; client-ip=115.124.103.27; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="dra-news@metastack.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of dra-news@metastack.com designates 115.124.103.27 as permitted sender) identity=mailfrom; client-ip=115.124.103.27; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="dra-news@metastack.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@relay.metastack.com) identity=helo; client-ip=115.124.103.27; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="postmaster@relay.metastack.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ag8FALAUEFBzfGcb/2dsb2JhbABFhS20NoEHgiABAQQBJxM/BQsCAQg2ECERJQIEDgUbh2MDBgUCAweyCA2JToplaIYUYAOTdYJoiXaFA4Jf X-IronPort-AV: E=Sophos;i="4.77,653,1336341600"; d="scan'208";a="168125578" Received: from relay.metastack.com ([115.124.103.27]) by mail1-smtp-roc.national.inria.fr with ESMTP; 25 Jul 2012 17:51:42 +0200 Received: from romulus.metastack.com ([81.102.132.77]) by relay.metastack.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 25 Jul 2012 16:40:30 +0100 Received: from remus.metastack.local (remus.metastack.com [172.16.0.1]) by romulus.metastack.com (8.14.2/8.14.2) with ESMTP id q6PFeO4L028162 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 25 Jul 2012 16:40:24 +0100 Received: from Remus.metastack.local ([fe80::547c:3c42:e1da:eda2]) by Remus.metastack.local ([fe80::547c:3c42:e1da:eda2%10]) with mapi id 14.02.0298.004; Wed, 25 Jul 2012 16:40:24 +0100 From: David Allsopp To: Diego Olivier Fernandez Pons CC: caml-list Thread-Topic: [Caml-list] JavaScript interpreter in OCaml Thread-Index: AQHNamrQ26IAWSPplEOopD2Q+5UOIZc6IsYe Date: Wed, 25 Jul 2012 15:40:23 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Organization: MetaStack Solutions Ltd. X-Scanned-By: MIMEDefang 2.65 on 172.16.0.20 X-OriginalArrivalTime: 25 Jul 2012 15:40:30.0931 (UTC) FILETIME=[D288BA30:01CD6A7B] Subject: Re: [Caml-list] JavaScript interpreter in OCaml On 25 Jul 2012, at 14:38, "Diego Olivier Fernandez Pons" wrote: > Does anyone have a JavaScript interpreter in OCaml ? Doesn't need to > be 100% compliant, the user can always rewritte some parts of the > JavaScript. And we discourage using weird / complex JavaScript > constructions anyway. Alternatively, a JavaScript -> OCaml source to > source translator could be good as well. I don't know whether you mean written in pure OCaml or just usable from OCa= ml. For the latter, I've used Alain Frisch's SpiderCaml: http://alain.frisc= h.fr/soft.html#spider Personally, I'd say that linking to a well-maintained interpreter is a bett= er solution than yet another implementation of JavaScript with all the wart= s that go with doing that. HTH, David=