Re: [Sigsafe-devel] Various issues
Status: Pre-Alpha
Brought to you by:
slamb
|
From: Scott L. <sl...@sl...> - 2006-05-11 01:46:57
|
On May 10, 2006, at 3:25 PM, Marcin 'Qrczak' Kowalczyk wrote: > Scott Lamb <sl...@sl...> writes: >> You're right on all points. I've made the fixes to the head revision >> in Subversion. When I get a chance to test everywhere, I'll make a >> new release. > > Thank you! I was worried that the project is dead :-) It's not dead but not as lively as I'd like. If any open source project of mine becomes hugely popular, I fear it won't be one designed to help Unix developers avoid subtle race conditions. The documentation's been a lot more successful than the code. I've occasionally noticed in my referrer logs people talking about it in languages I don't understand. (It was weird to see a bunch of _my_ code examples floating in a sea of Japanese text.) I've been meaning to bulk it out more. Probably the easiest thing to do would be just to introduce more asynchronous IO people to the self-pipe trick. It makes a lot of sense there. On the other hand, using sigsafe's code is much easier if you are doing synchronous operations (or you are writing a library which can be used for either). Reliable thread cancellation is probably the best example, especially considering that POSIX thread cancellation really doesn't work. Regards, Scott -- Scott Lamb <http://www.slamb.org/> |