[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>

33 messages 2000/02/08

[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>

Conrad writes:

13 messages 2000/02/15

[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>

17 messages 2000/02/19
[#1544] Re: Ruby/GTK and the mainloop — Yasushi Shoji <yashi@...> 2000/02/23

Hello Ian,

[#1550] Re: Ruby/GTK and the mainloop — Ian Main <imain@...> 2000/02/23

On Wed, Feb 23, 2000 at 02:56:10AM -0500, Yasushi Shoji wrote:

[#1516] Ruby: PLEASE use comp.lang.misc for all Ruby programming/technical questions/discussions!!!! — "Conrad Schneiker" <schneiker@...>

((FYI: This was sent to the Ruby mail list.))

10 messages 2000/02/19

[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>

The following message is a courtesy copy of an article

12 messages 2000/02/25

[ruby-talk:01558] Re: Ruby thread scheduling buglet

From: matz@... (Yukihiro Matsumoto)
Date: 2000-02-24 07:52:33 UTC
List: ruby-talk #1558
Hi,

In message "[ruby-talk:01551] Ruby thread scheduling buglet"
    on 00/02/23, Ian Main <imain@gtk.org> writes:

|You're going to like this one :)

Yes.  You even gave me a patch!  How pleasure it was.

|with the constant calling to sleep, it goes through this every call to
|rb_thread_schedule ().  The thread that was sleeping, wakes up probably just
|about every run through this function, so its set as the current thread.  It
|then loops about, goes to sleep again, and somewhere in there the next
|thread is run (thread 3 in our example), but then this one wakes up again
|before any others have a chance to run, and the scheduling is reset.

Well, I wanted to give high priority to just awaked thread, but I
guess it was too high.  To handle it properly, I have to implement
more complex thread scheduler, so I can compromise, at least for now.

Thank you.

							matz.

In This Thread