Defect Report concerning: IEEE Std. 1003.1-1996, ISO/IEC 9945-1:1996 - C API
Clause: P 226, Line 49, P 228, Line 105
PASC Interpretation Ref: pasc-1003.1-116
Topic: buffer sizes in characters or bytes


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  #116

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:			buffer sizes in characters or bytes
	Relevant Sections: P 226, Line 49, P 228, Line 105



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

        Date: 2000 June 16
	Ref: XSH 301


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

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

IEEE Std 1003.1-1996 (incorporates 1003.1-1990, 1003.1b-1993, 1003.1c-1995,
1003.1i-1995) (ISO 9945-1:1996)

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

 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):

P 226, Line 49
P 228, Line 105

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

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


"Characters" is not a measure of storage.  "Bytes" is.  Here storage,
not (potentially multi-byte) characters, is intended.


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

11  Solution proposed by the submitter (optional):

"characters" -> "bytes"

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



Interpretation response
------------------------
The standards states characters, and conforming implementations must conform
to this. However, concerns have been raised about this which are being
referred to the sponsor.


Rationale
-------------
None.

Notes to project editor (not part of the interpretation):
--------------------------------------------------------
Action the solution in section 11.

Forwarded to Interpretations group: 19 June 2000
Proposed resolution: 25 July 2000
Finalised Interpretation: 29 August 2000