[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strsignal module
From: |
Micah Cowan |
Subject: |
Re: strsignal module |
Date: |
Mon, 07 Jan 2008 18:05:07 -0800 |
User-agent: |
Thunderbird 2.0.0.9 (X11/20071031) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bruno Haible wrote:
> Colin Watson wrote:
>> 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.
>
> You were right. The set of signals that are supported everywhere is very
> small, namely:
> SIGINT
> SIGILL
> SIGFPE
> SIGSEGV
> SIGTERM
> SIGABRT
This, of course, is the set of signals required for any implementation
of C, regardless of platform.
I was under the impression that gnulib, or at least parts of it, was
only really intended to be portable to Unix-like systems. But then,
support for SIGALRM is required/expected for such.
Is there a general guideline for what constitutes "Gnulib's supported
platforms"?
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHgtpT7M8hyUobTrERAhpxAJ0TFY0x3uvhSNKhcP/rG7jdryc8rACgg1/v
vDzZ3aAz5QPXhAh7G7911w4=
=HUuR
-----END PGP SIGNATURE-----
Re: strsignal module, Bruno Haible, 2008/01/07