From: Cameron McBride <cameron.mcbride@...>
Date: 2010-05-08T06:25:50+09:00
Subject: Re: ease of porting (translating) ruby to C (vs. python)?

On Fri, May 7, 2010 at 16:02, Roger Pack <rogerpack2005@gmail.com> wrote:
>> Discussion on alternatives (Inline, using C extensions, NArray,
>> #include ruby, etc.) is welcome, but I'd like to keep the main focus
>> on translating to C for this thread.
>
> Rubinius is pretty fast these days..

and if you're familiar with C, inline or C extensions are really easy
once the bottlenecks are identified.

in my code, I've found that the number crunching can often be handled
by a function or two written as an extension, and then the beauty of
ruby can be used for main logic.

finally, I must admit that I agree with Seebs.  Porting code written
in either Python or Ruby to C is far from  trivial if there is any
complexity to the code.  The only way to make it easy is to use a
subset of the language capabilities and write procedurally.

Cameron