Hi Russ,
On Saturday 03 July 2010 18:49:40 Russ Allbery wrote:
> Here's a patch which implements that, plus an additional exception for
> libtool scripts which trap SIGPIPE by number. Objections or seconds?
> I'm copying Clint as posh maintainer since this will be relevant to which
> features posh implements.
Thanks for coming up with the wording.
> diff --git a/policy.sgml b/policy.sgml
> index bad28af..1658cbf 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -7427,7 +7427,19 @@ fname () {
> </example>
> must be supported and must set the value of <tt>c</tt> to
> <tt>delta</tt>.
> - </item>
> + </item>
> + <item>The XSI extension to <prgn>kill</prgn> allowing <tt>kill
> + -<var>signal</var></tt>, where <var>signal</var> is either
> + the name of a signal or one of the numeric signals listed in
> + the XSI extension (0, 1, 2, 3, 6, 9, 14, and 15), must be
> + supported.
> + </item>
> + <item>The XSI extension to <prgn>trap</prgn> allowing numeric
> + symbols must be supported. However, only the signal numbers
s/symbols/signals/ ?
> + listed in the extension, which are the same as
> + for <prgn>kill</prgn> above, plus SIGPIPE (13) must be
> + supported.
Why did you phrase the second sentence that way? why not something like "In
addition to the listed signal numbers, which are the same as for
<prgn>kill</prgn> above, SIGPIPE (corresponding to number 13) must be
supported?"
The list of signal numbers which are part of the XSI extension are well
defined, so there shouldn't be any reason to believe others are accepted too
(and avoids the use of 'only ... must be supported,' which I think is easier
to misinterpret.)
> + </item>
> </list>
> If a shell script requires non-SUSv3 features from the shell
> interpreter other than those listed above, the appropriate shell
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
Attachment:
signature.asc
Description: This is a digitally signed message part.