[#30995] [Bug #3523] win32 exception c0000029 on exit using fibers — B Kelly <redmine@...>

Bug #3523: win32 exception c0000029 on exit using fibers

19 messages 2010/07/02

[#31100] [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...>

Hello,

26 messages 2010/07/07
[#31148] Re: [rubysoc] Queue C-extension patch to come — Roger Pack <rogerdpack2@...> 2010/07/09

> As this it my first patch to Ruby, I don't know where to begin with.

[#31320] Re: [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...> 2010/07/16

Sorry for leaving this thread for so long. I've tried to finish the

[#31322] Re: [rubysoc] Queue C-extension patch to come — Aaron Patterson <aaron@...> 2010/07/16

On Sat, Jul 17, 2010 at 06:55:35AM +0900, Ricardo Panaggio wrote:

[#31324] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

NB: I am Ricardo's mentor for this project.

[#31331] Re: [rubysoc] Queue C-extension patch to come — Benoit Daloze <eregontp@...> 2010/07/17

On 17 July 2010 06:00, Caleb Clausen <vikkous@gmail.com> wrote:

[#31332] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

On 7/17/10, Benoit Daloze <eregontp@gmail.com> wrote:

[#31138] Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...>

Hi!

14 messages 2010/07/08
[#31146] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 7:04), Nikolai Weibull wrote:

[#31149] Re: Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...> 2010/07/09

On Fri, Jul 9, 2010 at 06:20, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#31150] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 18:28), Nikolai Weibull wrote:

[#31217] [Bug #3562] regression in respond_to? — Aaron Patterson <redmine@...>

Bug #3562: regression in respond_to?

14 messages 2010/07/12

[#31269] [Bug #3566] memory leak when spawning+joining Threads in a loop — Eric Wong <redmine@...>

Bug #3566: memory leak when spawning+joining Threads in a loop

14 messages 2010/07/13

[#31399] [Backport #3595] Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string — Dreamcat Four <redmine@...>

Backport #3595: Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string

17 messages 2010/07/21

[#31459] [Bug #3607] [trunk/r28731] Gem.path has disappeared? — Ollivier Robert <redmine@...>

Bug #3607: [trunk/r28731] Gem.path has disappeared?

22 messages 2010/07/23

[#31519] [Bug #3622] Net::HTTP does not wait to send request body with Expect: 100-continue — Eric Hodel <redmine@...>

Bug #3622: Net::HTTP does not wait to send request body with Expect: 100-continue

9 messages 2010/07/28

[ruby-core:31429] [rubysoc] Semaphore implementation

From: Ricardo Panaggio <panaggio.ricardo@...>
Date: 2010-07-22 01:30:02 UTC
List: ruby-core #31429
Hello,

This time I was working on Semaphore. It's on my semaphore branch
(http://github.com/panaggio/ruby/compare/queue...semaphore#files_bucket
although github is not comparing them correctly =/)

I'd like some feedback on the ruby implementation
(http://github.com/panaggio/ruby/compare/panaggio:queue...semaphore#diff-3)
and on the tests
(http://github.com/panaggio/ruby/compare/panaggio:queue...semaphore#diff-4).

Now I'm solving a lot of annoying bugs (racing conditions are horrible
to debug and solve =/) and polishing the code, but I know there's need
to more features, like Semaphore#broadcast and Semaphore#try_wait,
that I'll implement soon. But I need to know it there's anything more
missing, or anything that could be just removed (like num_waiting).

I don't think these tests can help me find problems on the code, but I
couldn't think about anything better. Any insight here you be very
appreciated.

This feedback will also help me a lot to implement it in C, as I'll
have a list of features and a direction to go to. I'll continue the C
implementation as soon as I can have the ruby implementation as a
reference (just to have something to test against - I'll try to
implement it in C using as much native code as possible).

There's some C code there (thread*), but it's very raw by now. Caleb
have told me about a lot of conceptual and implementation mistakes I
did, specially on thread_win32.c, and I know that there may be a lot
more. Any advice in here (if possible - I know it's a horrible code by
now)  will be also appreciated.

Again, thanks in advance for all the help. You all gave me a lot of
good insights  last time I asked.

Ricardo Panaggio

In This Thread

Prev Next