[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strsignal module
From: |
Colin Watson |
Subject: |
Re: strsignal module |
Date: |
Mon, 7 Jan 2008 21:44:02 +0000 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
On Mon, Jan 07, 2008 at 01:06:38PM -0800, Paul Eggert wrote:
> Thanks for tackling this. My kneejerk reaction: as a general rule, we
> prefer the differences between gnulib and the GNU C library to be
> localized to small sections of the code, and protected by #if !_LIBC,
> the idea being that ideally the gnulib and GNU C Library versions can
> be identical. Please see (for example) lib/mktime.c for how it's
> done.
Sounds reasonable; I'll recast it in that form. Thanks. It's unfortunate
that the lock and tls changes are messy, but I suspect thread-safety
does actually matter here. I may be able to simplify it, though.
Do you happen to know whether I was overdoing it by adding in #ifdefs
for SIGHUP, SIGINT, etc.? I decided better safe than sorry, but didn't
know whether there was some basic set of signals that Gnulib's supported
platforms were guaranteed to have.
--
Colin Watson address@hidden
Re: strsignal module, Bruno Haible, 2008/01/07