public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: William Ahern <william@25thandClement.com>
To: Ross Johnson <Ross.Johnson@homemail.com.au>
Cc: pthreads-win32@sourceware.org
Subject: Re: sigaction & pthread_sigmask
Date: Sat, 13 Sep 2008 23:40:00 -0000	[thread overview]
Message-ID: <20080913233928.GB16488@wilbur.25thandClement.com> (raw)
In-Reply-To: <485C7A15.30803@homemail.com.au>

On Sat, Jun 21, 2008 at 01:48:37PM +1000, Ross Johnson wrote:
> I'm not qualified to comment in detail.
> 
> One thing that I can say that may be important for you deciding how much 
> time you put into this is that a lot of effort has gone into keeping the 
> library portable and consistent (for performance) across Windows 
> versions from W95 onward (plus WinCE - or whatever it's called now), and 
> able to be built using at least the MSVC and GNU compilers going back a 
> few years (and others if possible) primarily as a C language library, 
> i.e. without exception handling. Although mildly discouraged, it can be 
> built easily with C++ EH, or SEH (MSVC only).

Update: Refactoring my code to better fit the existing codebase was more of
a hassle than I initially thought. Portability is less of an issue than, for
instance, refactoring my existing atomic operations library (which is based
on the proposed C++ standard, stdatomic.h).

I'll ping the list again when I restart work on this sub-project. My window
of time ran out, and I had to move onto other things.

      reply	other threads:[~2008-09-13 23:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19  5:58 William Ahern
2008-06-19 11:52 ` Burkhardt, Glenn
2008-06-19 12:15   ` John E. Bossom
2008-06-19 12:18     ` Burkhardt, Glenn
2008-06-20  1:29     ` Ross Johnson
2008-06-20 11:45       ` Burkhardt, Glenn
2008-06-20 11:48         ` drifting
2008-06-20  1:59 ` Ross Johnson
2008-06-20 21:39   ` William Ahern
2008-06-21  3:49     ` Ross Johnson
2008-09-13 23:40       ` William Ahern [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080913233928.GB16488@wilbur.25thandClement.com \
    --to=william@25thandclement.com \
    --cc=Ross.Johnson@homemail.com.au \
    --cc=pthreads-win32@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).