HomeAbout Us A-Z IndexSearch * Contact Us Register LoginPress Shop

The Open Brand -- Problem Reporting and Interpretations System


Problem Report 1438 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1438.


Report 1438 Actions


    Problem Report Number 1438
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0720
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1995-12-18 08:00
    Product Standard Internationalised System Calls and Libraries Extended (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.1.0
    Test Identification Headers/unistd.h 1
    Problem Summary TSD4U.00095 This test assumes _XOPEN_UNIX must be defined with a value. This is not mandatd by the spec.
    Problem Text
    The test assumes that _XOPEN_UNIX is defined and has a value.
    The definition for _XOPEN_UNIX says it is defined. It does not
    specify what value, it any it should have. (I believe it can be
    any value, including -1.)

    (This is additional information for additional review.)

    The basic problem is that the test suite assumes _XOPEN_UNIX is
    defined with a value. I believe that if _XOPEN_UNIX is defined,
    but has no value, that the implementation claims conformance to
    the X/Open UNIX Extension feature group. This fails the test.

    Section 1.3.5 of XSH does not specify what value _XOPEN_UNIX should
    take if the implementation claims conformance.

    (Notice that in section 1.3.4 it specifies that _XOPEN_ENH_I18N
    must be set to a value other than -1 if the implementation claims
    conformance to that feature group.)

    The definition of <unistd.h> states:

    Each of the following symbolic constants is defined only if the
    implementation supports the indicated revision of the X/Open
    Portability Guide:
    ...
    _XOPEN_UNIX X/Open CAE Specification, ...

    Please note here that _XOPEN_UNIX must be defined. There is no
    information that states what value, if any it should have. Section 1.3.5
    clearly states that if it has the value -1 then the feature is
    not supported. This contradicts the definition of _XOPEN_UNIX in
    <unistd.h>.
    Test Output
    TEST CASE: unistd.h

    Build tool error 2 on build of file /tset/CAPIheaders/hunistd/hunistd1
    hunistd1.c: In function `test1A':
    hunistd1.c:77: parse error before `=='
    hunistd1.c: At top level:
    hunistd1.c:81: parse error before `else'
    *** Error code 1

    Stop.

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    The XSH standard, section 1.3.5 states

    An implementation that does not claim conformance to this Feature
    Group will either set _XOPEN_UNIX to -1 (the preferred option) or
    leave it undefined (pre- dates the introduction of this Feature
    Group).


    We believe this implies that _XOPEN_UNIX must be defined to have
    a value if an implementation supports the X/Open UNIX Extension.

    Allowing an implementation to define _XOPEN_UNIX without giving
    it a value will make it difficult to portably test for this
    support.

    C source similar to the following

    if (_XOPEN_UNIX == -1)

    would fail to compile since the line would evaluate to

    if ( == -1)

    and cause a syntax error.

    The C preprocessor statement

    #if _XOPEN_UNIX == -1

    may also fail on platforms whose preprocessor does not meet the
    ISO C 9899:1990 spec.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    The test suite is testing outside of the specification. A Test Suite
    Deficiency should be granted.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   


Contact the Certification Authority