Email List: Xaustin-review-lX
[All Lists]

Defect in XBD 2.1.6

To: yyyyyyyyyyyyyyy@xxxxxxxxxxxxx
Subject: Defect in XBD 2.1.6
From: Geoff Clare <yyy@xxxxxxxxxxxxx>
Date: Mon, 26 Apr 2004 15:16:56 +0100
@ page 26-27 lines 1062-1070 section 2.1.6 objection [gwc option constants 1]

Problem:

Defect code :  1. Error

Section 2.1.6 "Options" has not been properly updated to account for
the new meaning of <unistd.h> option constants.  It only talks about
options being supported or not supported; it doesn't distinguish
between support indications made at compile time and at runtime.

Action:

Change:

    "The symbolic constants defined in <unistd.h>, Constants for
    Options and Option Groups reflect implementation options for IEEE
    Std 1003.1-2001. These symbols can be used by the application to
    determine which optional facilities are present on the
    implementation. The sysconf() function defined in the System
    Interfaces volume of IEEE Std 1003.1-2001 or the getconf utility
    defined in the Shell and Utilities volume of IEEE Std 1003.1-2001
    can be used to retrieve the value of each symbol on each specific
    implementation to determine whether the option is supported.

    Where an option is not supported, the associated utilities,
    functions, or facilities need not be present."

to:

    "The symbolic constants defined in <unistd.h>, Constants for
    Options and Option Groups reflect implementation options for IEEE
    Std 1003.1-2001. These symbols can be used by the application to
    determine which of three categories of support for optional
    facilities are provided by the implementation:

       1. Option never supported.

          The implementation advertises at compile time that the
          option will never be supported. In this case, the headers,
          data types, function interfaces and utilities required only
          for the option need not be present.

       2. Option always supported.

          The implementation advertises at compile time that the
          option will always be supported. In this case, all headers,
          data types, function interfaces and utilities required only
          for the option shall be available and shall operate as
          specified.

       3. Option might or might not be supported.

          The implementation does not advertise at compile time whether
          or not the option is supported. In this case, the fpathconf(),
          pathconf(), or sysconf() functions defined in the System
          Interfaces volume of IEEE Std 1003.1-2001 or the getconf
          utility defined in the Shell and Utilities volume of IEEE
          Std 1003.1-2001 can be used to retrieve the value of each
          symbol on each specific implementation to determine whether
          the option is supported.  All headers, data types, and
          function interfaces required to compile and execute
          applications which use the option at runtime (after checking
          at runtime that the option is supported) shall be provided,
          but if the option is not supported they need not operate as
          specified.  Utilities or other facilities required only for
          the option, but not needed to compile and execute such
          applications, need not be present."

<Prev in Thread] Current Thread [Next in Thread>