Dear Skaller!

I was not aware that you are behind the Felix project.
I really admire your achievments.

Ruby's classes are quite dynamic. There is a great deal of
reflexivity and onw can do a lot of metaprogramming and
nasty tricks like e.g. eval.

I don't plan my language to cope with all Ruby
finesses.  The programmer shoud use the interpreted pass
to do all the dirty hacks, the compiled functions would
would have a much more restricted repertoire.
E.g., I would not allow the user to do evals
in the type-checked part of the code. (Or,
alternatively the eval would be interpreted, but
for the first attempts, I would simply forbid it
together with other nasty features.)

I would not like to do any flow analysis. The main reason
 to use compilation is not performance, but type-safeness.
Today's computers are suitably efficient for most tasks. It's the
programmer's efficiency that should be improved.
(However, performance is still greatly improved over
interpreted Ruby or Python by the described transformations)
It is all mainly about reducing  programming and debugging
efforts.

I can program faster in Ruby for some tasks. This is mainly
because of the richer and more consistent syntax of Ruby and
its excellent and well designed class library. However as
a project grows, static typing in Ocaml saves me a lot of
debugging time. I would like combine these two different
advantages. Of course, performance should be improved when
possible.

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