From: "Frank Lesser [LSW]" Date: 2010-10-07T01:05:14+09:00 Subject: Re: how can we make a ruby compiler Ruby can be dynamically translated ( = jitted ) as Smalltalk is. A project "Rubinius" exists which goes in that direction. The problem with ruby is that it is not so easy ( = lot of work ) to write a ruby to bytecode translator. Smalltalk & List style languages are almost syntax free - the contrary is the case for Ruby. Or Smalltalk VM ( LSW-GVM ) runs Smalltalk at the speed of C/C++ and we plan to do that also for other dynamic languages ( e.g Haskell, JavaScript also Ruby ) in the nearest future. The LSW-GVM is currently available for Win32 ( deep GUI integration, multithreading ). We are working on a 64 Bit version. Frank Lesser "Tony Arcieri" schrieb im Newsbeitrag news:AANLkTinzm=ch-Vz8T6zFAa_xMoZq=4qavqYpQAqvm-n7@mail.gmail.com... > [Note: parts of this message were removed to make it a legal post.] > > On Tue, Oct 5, 2010 at 9:54 PM, Mohit Sindhwani wrote: > >> I tend to write Ruby code that avoids the advanced constructs of Ruby, >> making translation to C++ easier. >> > > This is pretty much a staple of static type inferencers for dynamic > languages that output C++... many language features simply cannot be > supported using this approach, most notably eval, and eval is pretty much > the most powerful tool for Ruby metaprogramming. Source translation to C++ > would preclude many of the things which make Ruby fun and interesting. > > -- > Tony Arcieri > Medioh! A Kudelski Brand >