a google search didn''t pull up much about threads in wxruby and most of it seemed to be around v 0.2.1...are threads working for wxruby now?
I think the question might be "are threads working in Ruby now?". Ruby has a Thread class, but it doesn''t use OS native threading. Instead, it has it''s own coopertative-threading system. These are like threads, except if one thread blocks, the other threads block too.... which I personally think makes them very un-like threads, but hey, what do I know. As Ruby doesn''t support multithreaded operation, I think it would be very dangerous to assume wxThread would pop in. If the interpreter has any global state (or even unprotected shared state) things would go downhill in a hurry. Hope that helps, Nick tony summerfelt wrote:>a google search didn''t pull up much about threads in wxruby and most >of it seemed to be around v 0.2.1...are threads working for wxruby >now? > >_______________________________________________ >wxruby-users mailing list >wxruby-users@rubyforge.org >http://rubyforge.org/mailman/listinfo/wxruby-users > > >. > > >
Well, I''ve used Ruby Threads in my apps with wxruby, and they''ve worked ok except for the blocking issue. Since the Ruby app is all in the same thread context, it doesn''t disrupt the wx event handlers. Nick tony summerfelt wrote:>On Tue, 29 Jun 2004 08:18:38 -0500, you wrote: > > > >>I think the question might be "are threads working in Ruby now?". >> >> > >:) i guess my answer would be ''my application uses ruby threads ok'' > >will l throwing a wxruby interface on it break it? > > > >>Ruby has a Thread class, but it doesn''t use OS native threading. >> >> > >ruby thread''s are working well for me, and i wasn''t that worried about >the underlying implementation. i''ve used wxWidgets for other projects, >so it was a natural to use them for my ruby app. i''d like to avoid tk >for the interface but i may be forced to if the threading is going to >be a problem... > > > > >. > > >