Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!feeder.news-service.com!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!talisker.lacave.net!lacave.net!not-for-mail From: -= Ko =- Black Ninja Newsgroups: comp.lang.ruby Subject: Re: How to call Ruby from non-interpreter native thread? Date: Tue, 5 Apr 2011 02:31:36 -0500 Organization: Service de news de lacave.net Lines: 9 Message-ID: <49bf6e4814c28b440e2c22fefe2d95dd@ruby-forum.com> References: <3d387397bafae9b859872a3f17cb679c@ruby-forum.com> NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: talisker.lacave.net 1301988714 95057 65.111.164.187 (5 Apr 2011 07:31:54 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Tue, 5 Apr 2011 07:31:54 +0000 (UTC) In-Reply-To: <3d387397bafae9b859872a3f17cb679c@ruby-forum.com> X-Received-From: This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway X-Mail-Count: 380962 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: <49bf6e4814c28b440e2c22fefe2d95dd@ruby-forum.com> Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:2301 I've got skill with GIL (Global Interpreter Lock) and used rb_thread_blocking_region() function. So, this thread can be close now... thanx to myself =)) -- Posted via http://www.ruby-forum.com/.