------art_38413_2424236.1197591040323
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You can read something here:
http://www.infoq.com/news/2007/05/ruby-threading-futures

On Dec 13, 2007 9:25 PM, Just Another Victim of the Ambient Morality <
ihatespam / hotmail.com> wrote:

>    I fear many of my questions will belong to the "often asked" category
> but a google search wasn't too fruitful so here I am...
>
>    I did find some information on the state of threading but I wanted to
> clear some things up.  If Ruby 1.9 will use system threads, what will
> happen
> to the green threads?  What will happen to libraries that require green
> threads, like generator.rb?  Will they end up using system threads?
>    If Ruby is using system threads, does that mean Ruby will be thread
> safe?  That is, will we be able to call into an embedded Ruby interpreter
> from multiple threads?
>
>    Matz's most "regretting" behaviour of Ruby is that block variables are
> local to the block.  Will this be changed in Ruby 1.9?  If so, how will
> that
> affect threads, since they're made from blocks?  Will thread variables
> just
> leak right out into the defining scope?
>
>    Finally, if Ruby will now be compiled into bytecode, will we be able to
> run the bytecode without the Ruby source?  Will Ruby be able to do this in
> an embedded application?
>
>    These are what are on my mind, at the moment.  If I think of any
> others,
> I'll add them to this thread.
>    Thank you...
>
>
>
>


-- 
Regards,
Luiz Vitor Martinez Cardoso [Grabber].
(11) 8187-8662

Eletrical Engineer at maua.br

------art_38413_2424236.1197591040323--