From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ober.14@osu.edu>
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr
X-Spam-Level: **
X-Spam-Status: No, score=2.2 required=5.0 tests=AWL,DNS_FROM_SECURITYSAGE,
	SPF_NEUTRAL autolearn=disabled version=3.1.3
X-Original-To: caml-list@yquem.inria.fr
Delivered-To: caml-list@yquem.inria.fr
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105])
	by yquem.inria.fr (Postfix) with ESMTP id ADBBABBAF
	for <caml-list@yquem.inria.fr>; Tue, 18 Nov 2008 04:44:11 +0100 (CET)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgBAFfIIUlDWxLCbmdsb2JhbACBbZFpPrI/hh6EO4J5
X-IronPort-AV: E=Sophos;i="4.33,622,1220220000"; 
   d="scan'208";a="31546092"
Received: from ip67-91-18-194.z18-91-67.customer.algx.net (HELO server1.bertec.net) ([67.91.18.194])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 18 Nov 2008 04:44:10 +0100
Received: from kuba.bertec.net (kuba.bertec.net [192.168.2.16])
	by server1.bertec.net (Postfix) with ESMTP id 435A110573C
	for <caml-list@yquem.inria.fr>; Mon, 17 Nov 2008 22:44:09 -0500 (EST)
From: Kuba Ober <ober.14@osu.edu>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [announce] O'Browser : OCaml on browsers
Date: Mon, 17 Nov 2008 22:43:52 -0500
User-Agent: KMail/1.9.10
References: <492199E2.1020504@gmail.com>
In-Reply-To: <492199E2.1020504@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200811172244.01033.ober.14@osu.edu>
X-Spam: no; 0.00; ocaml:01 ocaml:01 runtime:01 ocaml's:01 bindings:01 bug:01 cheers:01 javascript:98 javascript:98 threads:01 wrote:01 caml-list:01 functions:01 oop:01 benjamin:01 

On Monday 17 November 2008, Benjamin Canou wrote:

> O'Browser is an implementation of the OCaml virtual machine in
> JavaScript, designed to run in web browsers.
> It features a runtime library compatible with OCaml's standard one
> (including OOP and concurrent threads) and bindings of some JavaScript
> functions to manipulate the DOM primitives.
[...]
> Please note that this is an early version, in particular the DOM
> interface module is neither pretty nor well typed.
> However, it can already be used to create little applets or scripts (as
> in the tutorial [2], the examples of the distribution [3] or my webpage
> [4]) and we'll be glad to receive your comments or bug reports.

And the reason is?....

Pardon the question, but is this meant to be "useful" in the future,
or is it just a fun experiment (in which case the next target should
be brainfuck).

My question (why and what for?) is serious, though.

Cheers, Kuba