Defect Report concerning: IEEE Std. 1003.2-1992, ISO/IEC 9945-2:1993 - Shell & Utilities
Clause: 2.13
PASC Interpretation Ref: pasc-1003.2-01
Topic: Symbolic limit macros


This is an unapproved interpretation of PASC 1003.2-1992, ISO/IEC 9945-2:1993 - Shell & Utilities.

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

Last update: 20 April,2001


								1003.2-92  #1

	Class: Editorial defect

This will be forwarded to the IEEE for incorporation into a future 
errata sheet for the document, as well as an IEEE interpretations
publication, and will be also made available on-line on the IEEE 
SPAsystem.
 _____________________________________________________________________________


	Interpretation Number:	(to be assigned by the IEEE)
	Topic:			Symbolic limit macros
	Relevant Sections:	2.13


Interpretation Request: (Defect Report)
-----------------------
 
          In Section B.2 - C Numerical Limits, the standard states: 
               The following subclauses list the names of  macros 
               that C language applications  can  use  to  obtain 
               minimum and current values for limits  defined  in 
               2.13.1. 
          [Draft 12 of IEEE Std 1003.2-1992 (July 1992), p. 759, lines 
          93-94] 
 
          Then in Section B.2.3 -  Execution-Time  Symbolic  Constants 
          for Portability Specifications, Table B-5 lists  C  language 
          macros with names strikingly  similar  to  POSIX.2  optional 
          facility  configuration  parameters,  defined   in   Section 
          2.13.2.   Table  B-5  misses  the  configuration   parameter 
          {POSIX2_C_BIND}. 
 
 
          Is the intent of the standard  that  all  the  variables  in 
          Section 2.13.2 as well as Section 2.13.1 have  corresponding 
          variables in the C binding, since seven of  these  variables 
          are listed in Table B-5? 


IEEE Interpretation for 1003.2-1992
-----------------------------------

As the Standard does not list _POSIX2_C_BIND among the symbols in the
table in Table B-5, a conforming implementation is not required to support
this symbol in the manner described by Section B.2.3. This should not be
construed to prohibit conforming implementations from supporting
_POSIX2_C_BIND in the manner described, as an extension. Concerns about
this are being referred to the Sponsor.

Rationale for Interpretation:
-----------------------------

In Section B.2, the intent of the standard is made clear, that the
symbols from Section 2.13.1 are to be listed here as well. It appears
that the exclusion of this one symbol is an editing defect in the
standard.

 _____________________________________________________________________________