caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: Thomas Fischbacher <t.fischbacher@soton.ac.uk>
Cc: Mehdi Dogguy <mehdi.dogguy@pps.jussieu.fr>,
	OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] adding a scripting language to an ocaml program
Date: Tue, 06 Jul 2010 23:01:44 +0200	[thread overview]
Message-ID: <4C3399B8.90401@citycable.ch> (raw)
In-Reply-To: <4C3208C2.3090803@soton.ac.uk>

Thomas Fischbacher a écrit :
> 
> The last thing I remember is that Guillaume had contacted me about
> wanting to re-write it, but not much seems to have happened on that
> front so far.

Well, things have happened on this front so far. And a few people have 
the code that I've written. Unfortunately, for rather awkward reasons, I 
am not in a position to release it. But hope to be in the rather not 
distant future.

It's basically a rewrite. It works, but isn't fully featured yet. I 
believe memory management is done properly. There are also some C 
varargs functions in the Python API that have been properly binded with 
the libavr library (or something called like that). A (yet basic) syntax 
extension allows to write things like:

	module X = python module mypython module

It does introspection and dumps the OCaml code needed to access values 
of the module. I've been hitting type inference issues in Python for 
this. But there is some work (like shedskin) to capitalise in order to 
make the syntax extension more interesting when it comes to typing.

And there's a Debian package, also.

Do not hold your breath on this code, as a release might take a while.

But if someone is willing to carve out of shedskin the code needed to do 
type inference and bind it to OCaml, that would be a nice contribution 
to the syntax extension.

I do not have much time available on this one, and I currently have 
other interests. But if someone is interested in the code, please email 
me to see what is possible to do...

All the best,

Guillaume Yziquel.
-- 
      Guillaume Yziquel
http://yziquel.homelinux.org/


  parent reply	other threads:[~2010-07-06 21:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03 18:34 Martin DeMello
2010-07-03 18:43 ` Michael Ekstrand
2010-07-03 18:56   ` [Caml-list] " Martin DeMello
2010-07-03 19:06     ` Michael Ekstrand
2010-07-03 19:35     ` [Caml-list] " David Allsopp
2010-07-03 18:52 ` [Caml-list] " Lukasz Stafiniak
2010-07-03 18:53   ` Vincent Aravantinos
2010-07-03 19:05     ` Martin DeMello
2010-07-03 19:02   ` Martin DeMello
     [not found]     ` <AANLkTinIbSSrxtuWrwv16_XIo2MU2hdhjHhrIORSFUPN@mail.gmail.com>
2010-07-03 21:15       ` Martin DeMello
2010-07-03 20:42   ` malc
2010-07-03 19:16 ` David Powers
2010-07-04 19:54 ` Goswin von Brederlow
2010-07-05 12:41   ` Florent Monnier
2010-07-05 13:14 ` Thomas Fischbacher
2010-07-05 16:13   ` Mehdi Dogguy
2010-07-05 16:30     ` Thomas Fischbacher
2010-07-05 18:02       ` Mehdi Dogguy
2010-07-08 15:22         ` Thomas Fischbacher
2010-07-08 16:00           ` Mehdi Dogguy
2010-07-06 21:01       ` Guillaume Yziquel [this message]
2010-07-06 21:08         ` Guillaume Yziquel
2010-07-06 10:38 ` Richard Jones
2010-07-06 12:55   ` Martin DeMello

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=4C3399B8.90401@citycable.ch \
    --to=guillaume.yziquel@citycable.ch \
    --cc=caml-list@yquem.inria.fr \
    --cc=mehdi.dogguy@pps.jussieu.fr \
    --cc=t.fischbacher@soton.ac.uk \
    /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).