This is the mail archive of the mailing list for the pthreas-win32 project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: sigaction & pthread_sigmask

I think so.  Semaphores might seem out of scope, but they're an integral
part of concurrent programming.  Signals need to be thread smart, so
they're naturally part of a thread implementation.
So are timers - attached is a pthreads compatible version of Posix
timers, but it's lacking the function of sending a signal to a thread
when a timer has expired. 

> -----Original Message-----
> From: 
> [] On Behalf Of 
> William Ahern
> Sent: Thursday, June 19, 2008 1:58 AM
> To:
> Subject: sigaction & pthread_sigmask
> Would it be worthwhile to submit a sigaction, sigwait, 
> sigprocmask, pthread_sigmask patch? Or are signals strictly 
> outside the scope of the project?
> I'm working on sigaction and sigwait implementations--using 
> atomic CAS operations for async-safety--intended for a 
> portable kqueue library. But the library depends on 
> pthreads-w32 anyhow, and it would be cleaner to simply patch upstream.

Attachment: pthreads-timer.tbz
Description: pthreads-timer.tbz

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]