[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bashisms
|
From: |
Eric Blake |
|
Subject: |
Re: bashisms |
|
Date: |
Wed, 19 May 2010 09:01:22 -0600 |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Lightning/1.0b1 Mnenhy/0.8.2 Thunderbird/3.0.4 |
On 05/19/2010 12:30 AM, Ralf Wildenhues wrote:
>> POSIX requires signals specified as names (HUP, INT, etc),
>> although XSI allows numbers for certain signals (the ones used by
>> gnulib all fall into this category).
>
> We've had a similar discussion about this on an Autoconf list a while
> ago (with a Debian maintainer). The Autoconf manual, Shell Portability
> chapter, lists 1 2 13 15 as signals which are safe to trap. I'm not
> aware of any shell which does not accept these signal numbers in
> practice, except for maybe one that was written specifically to inflict
> extra pain upon shell script authors by explicitly disallowing them.
For a further analysis:
ash on cygwin understands _only_ numbers, not names.
posh on debian understands _only_ names, not numbers.
But ash on cygwin is quite old, and posh falls in the category of shells
that inflict extra pain upon shell script authors.
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature