Defect Report concerning: IEEE Std. 1003.1-1996, ISO/IEC 9945-1:1996 - C API
Clause: 7.1.1.9 lines 246-250
PASC Interpretation Ref: pasc-1003.1-93
Topic: ICANON


This is an unapproved interpretation of PASC 1003.1-1996, ISO/IEC 9945-1:1996 - C API.

Use of the information contained in this unapproved document is at your own risk.

Last update: 10 April,2001


								1003.1-96  #93

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:			ICANON
	Relevant Sections:	7.1.1.9 lines 246-250


PASC Interpretation Request: (Defect Report)
----------------------------  

	Date: 1998 Sep 8

------------------------------------------------------------------------ 

 7  Defect Report concerning (number and title of International Standard
    or DIS final text, if applicable): 

System Interface Standard:IEEE Std 1003.1-1990 (ISO 9945-1:1990)

------------------------------------------------------------------------ 

 8  Qualifier (e.g. error, omission, clarification required):

1

Error=1 , Omission=2, Clarification=3

------------------------------------------------------------------------ 

 9  References in document (e.g. page, clause, figure, and/or table
    numbers):

7.1.1.9 lines 246-250

------------------------------------------------------------------------ 

10  Nature of defect (complete, concise explanation of the perceived
    problem):


Clause 7.1.1.9 lines 246-250 conflicts with clause 7.1.2.2 lines 351-352 with respect to the relevance of ICANON to the translation of CR to NL on input.

Lines 246-250 state that ICANON must be set as a necessary precondition to the translation of CR to NL on input. Lines 351-352 do not mention ICANON as a precondition for this mapping.

Note that historical practice (BSD and System V) agree with 7.1.2.2 lines 351-352. Note also that the definition of ICANON (7.1.2.5 line 434 and lines 450-452) indicates ICANON is associated with erase and kill processing, character echo processing, and line assembly; not with input character mapping.

------------------------------------------------------------------------ 

11  Solution proposed by the submitter (optional):

Ask the relevant committee to recognize, in a future revision of 1003.1, that the mention of ICANON in lines 246-250 is erroneous.

State that the conformance of an implementation cannot be affected by its behavior with respect to ICANON having an effect on mapping of CR to NL on input, and that portable applications cannot rely on any such effect.


------------------------------------------------------------------------ 

Interpretation Response:
-----------------------

There is no conflict, clause 7.1.1.9 refers to  ICANON and the reference is 
strictly redundant.  Existing practise does do the translation when 
ICANON is turned off.

Rationale:
----------
None


Forwarded to Interpretations group: 10 Sept 1998
Proposed Interpretation: 26 Oct 1998
Finalised Interpretation: February 17 1999