WG15 Defect Report Ref: 9945-2-07
Topic: ed

This is an approved interpretation of 9945-2:1993.


Last update: 1997-05-20


	Class: No change.


	Topic:			ed
	Relevant Sections:

Defect Report:
          In Section  -  Asynchronous  Events  {of  ed},  the 
          standard states: 
               The ed utility shall take the standard action  for 
               all signals (see,  with  the  following 
                    SIGINT    [...] 
                    SIGHUP    [...] 
          [Draft 12 of ISO/IEC 9945-2:1993 (July 1992), p. 274, lines 
          The SIGQUIT signal is not explicitly mentioned in  the  list 
          that followed the above statement.  Does the standard really 
          mean that ed cannot clean up or otherwise handle  a  SIGQUIT 
          According to Section 1.1 - Scope: 
               The facilities provided are  based  on  historical 
               models of the following documents:  the  System  V 
               Interface Definition {B35}; the  BSD  User  Manual 
               {B41}; the x/OPEN  Portability  Guide  {B44};  and 
               documentation for the KornShell  {B36}.   Emphasis 
               is placed on standardizing existing  practice  for 
               existing users, with changes or additions  limited 
               to correcting deficiencies in the following areas: 
                    (a)  Support for international character sets 
                         and  other  localization   requirements, 
                         such   as   date   formats,    collation 
                         sequences, etc.. 
                    (b)  Reconciliation  of  differences  between 
                         the historical implementations. 
                    (c)  Elimination   of   system   or    device 
                    (d)  Corrections  of  features   that   could 
                         reduce       system       or        user 
          [Ibid., p. 2, lines 35-47] 
          Disallowing the ed utility from intercepting SIGQUIT is  not 
          historical practice, and is likely to upset  existing  users 
          of existing utilities.  Is the omission of SIGQUIT from  the 
          list in Section simply an  oversight?   It  is  our 
          belief that any production-level interactive command  should 
          ignore a SIGQUIT signal. 

WG15 response for 9945-2:1993 

The standard clearly requires that the utility to perform as if it had
taken the standard action upon receipt of SIGINT, by reference to
Section, option 3.  Thus the utility is allowed to perform
cleanup actions as long as it meets the requirements of

Rationale for Interpretation: