Version française
Home     About     Download     Resources     Contact us    
Browse thread
Re: [Caml-list] Looking for collaborators on a hobby project
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: skaller <skaller@u...>
Subject: Re: [Caml-list] Looking for collaborators on a hobby project
On Fri, 2004-05-28 at 07:11, Christian Szegedy wrote:
> Dear Skaller!
> 
> Is the Vyper project public?
> 
> I could not find any version of Vyper on the net. :(

It used to be on Sourceforge, but it's gone now
and I don't have a copy myself. What it did
was interpret the AST directly.

> You have written, that the analyis of the type information
> turned out be difficult. I can believe this. :)

For Python. Functions like 'eval' really make it
hard. Python has deprecated 'eval(str)' now: you're
supposed to use 'eval(str, dict)' so the dict
captures the dynamic variables instead of the current
scope. locals() hasn't work for ages due to compiled
function locals (special fast fetch bytecode).

But it is still very hard: Python class and objects are
also both dynamically extensible.

> Suppose, we have the following Ruby class:

I've never seen a Ruby program before. I have no idea
how dynamic it is..?

> After that, OCaml would take care of all the typing stuff...

Yes, but it won't help you optimise integer addition:
you'll have to do some special checks yourself,
and modify the generated Ocaml so it knows when
something is an integer.

> 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...

Alternatively you can try to do flow analysis to see
which variables can't be nil, ever, and change their
type from 'a myref to 'a. Ocaml will propagate the typing
and your result will be optimised .. but you will need to change
all uses to match .. meaning you'll have to do type analysis
yourself .. Ocaml will check your analysis, but it won't
do it for you.

In Felix I do this kind of thing, and the generated C++
is again type checked by  g++, so only casting errors
tend to escape early detection. Its very nice to check
your static type checking with someone else's static
type checker :)

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net



-------------------
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