Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 0456 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 0456.

Report 0456 Actions

    Problem Report Number 0456
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0075
    Raised 1994-06-14 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries (XPG4)
    Certification Program The Open Brand certification program
    Test Suite VSX4 version 4.3.4
    Test Identification XPG4.os/time/strptime 5
    Linked Problem Reports err.4.3.3.061, (in, old, system)
    Problem Summary PG4R.076 This was reported to vsx_support during the beta testing of VSX 4.3.3 and accepted as a test suite deficiency. The fix was not expected to make VSX 4.3.4. Below is the supportive information included ...
    Problem Text
    This was reported to vsx_support during the beta testing of VSX 4.3.3 and
    accepted as a test suite deficiency. The fix was not expected to make
    VSX 4.3.4. Below is the supportive information included with the
    original error report.

    The testcases below are failing for unknown reasons . I tested our
    implementation of strptime() using the following procedure.

    1) Create a tm structure, initialize with testcase expected values
    2) Use strftime(character array,size,format string,tm struct) to
    convert expected values to a character string in the locale required
    (i.e. VSX4L1 or VSX4L2)
    3) Use the character array in a call to strptime with same format string; i.e.
    strptime(character array,format string,other tm struct).
    4) Compare new tm struct values to the expected values.

    In testing the dates/times and format strings in the testcases above,
    our strptime() returned the expected values.

    vsx_support response:

    This is obviously related to your earlier report WLT11 (err.4.3.3.059).
    The D_T_FMT, D_FMT and T_FMT language constants for VSX4L1 and VSX4L2
    contain ASCII spaces between the conversion directives. The ASCII spaces
    are not treated as whitespace by your strptime(), so it does not match
    them against the \100 characters in the input string.

    It looks as though other implementors have got round this problem by
    treating ASCII space characters in the format string as whitespace, even
    though isspace() would say they are not. This would explain why they
    do not see the problem you reported in WLT11 (err.4.3.3.059).

    We could probably fix the problem by changing the VSX4L1 and VSX4L2
    definitions to use \100 characters instead of ASCII spaces in D_T_FMT,
    D_FMT and T_FMT. However, we would like this issue to be discussed by
    the relevant X/Open technical groups before we make such a drastic change.


    Test Output
    ******************************************************************************
    /tset/XPG4.os/time/strptime/T.strptime 5 Failed

    Test Description:
    If strptime() is supported:
    When format is a string containing the following field descriptors:
    a. a or A abbreviated or full weekday name - eg. Sun to Sat or
    Sunday to Saturday
    b. b, B or h abbreviated or full month name - eg. Jan to Dec or
    January to December
    c. c appropriate date and time as specified in the D_T_FMT string
    d. p AM/PM string as specified in the AM_STR/PM_STR
    e. x appropriate date as specified in the D_FMT string
    f. X appropriate time as specified in the T_FMT string
    then a call to strptime() reads characters from string and, in the
    case that these characters match the format of the directive,
    translates these characters into the appropriate member of the tm
    structure.
    Otherwise:
    A call to strptime() returns NULL and sets errno to ENOSYS.

    Test Strategy:
    PARENT process will
    CREATE child process using cppair()
    CHILD process will
    SET the locale for LC_TIME to VSX4L1
    FOR each day format
    FOR each full weekday name
    GET the relevant string using pslanginfo()
    INITIALISE the tm structures
    VERIFY that strptime() performs as expected
    FOR each abbreviated weekday name
    GET the relevant string using pslanginfo()
    INITIALISE the tm structures
    VERIFY that strptime() performs as expected
    FOR each month format
    FOR each full month name
    GET the relevant string using pslanginfo()
    INITIALISE the tm structures
    VERIFY that strptime() performs as expected
    FOR each abbreviated month name
    GET the relevant string using pslanginfo()
    INITIALISE the tm structures
    VERIFY that strptime() performs as expected
    FOR format strings D_T_FMT, AM_STR, D_FMT, and T_FMT:
    INITIALISE the tm structures
    VERIFY that strptime() performs as expected
    REPEAT everything contained above in this test for the locale
    VSX4L2

    Test Information:

    appropriate date and time as specified in D_T_FMT string
    strptime("6.42.21 NM 09\05705\05791", "%c", &testbuf) failed.
    Current language is VSX4L1
    return value was NULL

    appropriate date and time as specified in D_T_FMT string
    strptime("5 9 1991 6'42'21", "%c", &testbuf) failed.
    Current language is VSX4L2
    return value was NULL

    appropriate time as specified in T_FMT string
    strptime("6.42.21 NM", "%X", &testbuf) failed.
    Current language is VSX4L1
    return value was NULL

    appropriate date as specified in D_FMT string
    strptime("05 09 1991", "%x", &testbuf) failed.
    Current language is VSX4L2
    return value was NULL

    ******************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The previous request (reference req.4.2.352) also asked for this
    test to be considered faulty. There is no need to make a second
    application for a waiver on the same test.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority