Okhay, I see the point. But then what's the current, working method of 
running ordinary and arbitrary Ruby code inside an application?

mortee

On 2015.04.02. 20:47, Carlo E. Prelz wrote:
> 	Subject: Re: embeddig ruby in a C application
> 	Date: gio 02 apr 15 08:19:16 +0200
>
> Quoting mortee (mortee.lists / kavemalna.hu):
>
>> This is nice, and works like a charm. But so far itt seems to me that Mruby
>> can only use gems specifically targeted for it, and even those have to be
>> specified at build time. Actually, I'd like to give more or less free hand
>> to the users of my app with regards to the ruby code they want to execute.
>>
>> So how would I go about using regular gems, especially stuff like
>> ActiveSupport? And how can I not have to know these at build time?
> Mruby is a different beast from MRI Ruby. It is targeted to different
> usage models (specifically to the embedded world), it does not plan to
> substitute Ruby altogether.
>
> The design of Mruby is surprisingly elegant. Every source tree is
> self-enclosed, so that you can have as many versions coexisting on
> your machine, including exactly what you need for that specific
> run. The procedure is a little bit less automatic, but it gains in
> flexibility.
>
> If you need ActiveSupport, and find the mechanism of plain Ruby gems
> necessary for your needs, then you'd better use MRI. Mruby certainly
> offers simple gems for database access (I currently use Redis), but
> feeding it with behemoth packages like those that make up the Rails
> world goes (I hope) against the scope of that project.
>
> Carlo
>