From: "Stephen Weeks" <sweeks@sweeks.com>
To: "David Teller" <David.Teller@univ-orleans.fr>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] JavaScript parser
Date: Thu, 31 May 2007 16:13:14 -0400 [thread overview]
Message-ID: <604682010705311313j10b71c4fq387fa4fe1f80d453@mail.gmail.com> (raw)
In-Reply-To: <1180641737.6053.17.camel@Blefuscu>
> Does anyone know of a JavaScript parser for OCaml ? This would save me some
> work towards the development of a JS static checker.
I know of one in SML, which might be easier to port than to start from scratch.
http://mlton.org/cgi-bin/viewsvn.cgi/mltonlib/trunk/com/entain/javascript/unstable/
Also, the Mozilla guys are implementing the Ecmascript 4 spec in SML. They are
pretty far along as I understand it. They must have some kind of JS parser
implemented in SML too. You might ask on the ES4 list.
https://mail.mozilla.org/listinfo/es4-discuss
next prev parent reply other threads:[~2007-05-31 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 20:02 David Teller
2007-05-31 20:13 ` Stephen Weeks [this message]
2007-05-31 20:21 ` [Caml-list] " Joel Reymont
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=604682010705311313j10b71c4fq387fa4fe1f80d453@mail.gmail.com \
--to=sweeks@sweeks.com \
--cc=David.Teller@univ-orleans.fr \
--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