From: szegedy@t-online.de (Christian Szegedy)
To: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Looking for collaborators on a hobby project
Date: Thu, 27 May 2004 23:11:34 +0200 [thread overview]
Message-ID: <40B65986.2030603@t-online.de> (raw)
Dear Skaller!
Is the Vyper project public?
I could not find any version of Vyper on the net. :(
You have written, that the analyis of the type information
turned out be difficult. I can believe this. :)
However, this is something already solved. In fact,
this is solved in Ocaml! So, I would not have to solve it
directly.
Now, my idea is the following:
Suppose, we have the following Ruby class:
class A
def f(x,y)
x.g(y,@a)
end
def h(x)
f(@b,v)
end
end
Then the interpreter would simply transform it to the following OCaml
class:
type 'a myref = Nil | Obj of 'a
let use x = match x with
| Obj x -> x
| Nil -> failwith "Dereferencing nil"
class ['f_x,'f_y,'h_x,'a,'b] a =
object(self)
val mutable a:('a myref) = Nil
val mutable b:('b myref) = Nil
method f ( x : 'f_x) (y : 'f_y) = (use x)#g y a
method h ( v : 'f_x) = self#f b v
end
After that, OCaml would take care of all the typing stuff...
Of course using the myref class comes with a performance penalty also.
This can be eliminated if one does not allow nil at all: that is all
instance variables must have valid default value.
I think, this is a good idea anyway...
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2004-05-27 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 21:11 Christian Szegedy [this message]
2004-05-27 22:09 ` skaller
2004-05-27 23:00 ` Christian Szegedy
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 20:21 Christian Szegedy
2004-05-26 21:36 ` Brandon J. Van Every
2004-05-26 21:37 ` Richard Jones
2004-05-28 9:17 ` Richard Zidlicky
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=40B65986.2030603@t-online.de \
--to=szegedy@t-online.de \
--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