21 messages in org.ruby-lang.ruby-talkRe: C Threads and Ruby
FromSent OnAttachments
Kroeger, Simon (ext)Jun 20, 2006 3:27 am 
Patrick HurleyJun 20, 2006 4:28 am 
Kroeger, Simon (ext)Jun 20, 2006 4:59 am 
Francis CianfroccaJun 20, 2006 5:13 am 
Patrick HurleyJun 20, 2006 9:39 am 
Paul BrannanJun 20, 2006 11:33 am 
Patrick HurleyJun 20, 2006 1:16 pm 
Francis CianfroccaJun 20, 2006 1:17 pm 
Francis CianfroccaJun 20, 2006 1:19 pm 
Simon KrögerJun 20, 2006 2:29 pm 
Joel VanderWerfJun 20, 2006 2:35 pm 
Francis CianfroccaJun 20, 2006 2:39 pm 
Bill KellyJun 20, 2006 2:42 pm 
Simon KrögerJun 20, 2006 2:49 pm 
Francis CianfroccaJun 20, 2006 3:26 pm 
Francis CianfroccaJun 20, 2006 3:34 pm 
Bill KellyJun 20, 2006 4:08 pm 
Francis CianfroccaJun 20, 2006 5:07 pm 
Kroeger, Simon (ext)Jun 21, 2006 2:53 am 
Francis CianfroccaJun 21, 2006 3:15 am 
Paul BrannanJun 22, 2006 8:21 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: C Threads and RubyActions...
From:Joel VanderWerf (vjo@path.berkeley.edu)
Date:Jun 20, 2006 2:35:05 pm
List:org.ruby-lang.ruby-talk

Simon Kröger wrote:

Francis Cianfrocca schrieb:

I typically use a pipe for this kind of synchronization.

Me too. Crude but it works.

Well, b*****it: (sorry, no offense intended...)

------------------------------- $stdout.sync = true rd, wr = IO.pipe

Thread.new do loop do puts 'foo!'

Might help:

wr.puts 'foo!'

sleep 0.5 end end

sleep 2 puts(rd.gets) -------------------------------

ruby 1.8.4 (2005-12-24) [i386-mswin32] gives me 4 foo!s and waits for the rest of eternity. So blocking on a pipe isn't an option for platform independent code. (or am I doing something wrong, please say I'm doing something wrong!)

cheers

Simon

-- vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407