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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1280 Actions

    Problem Report Number 1280
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0562
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1998-09-08 08:00
    Product Standard Internationalised Terminal Interfaces
    Certification Program The Open Brand certification program
    Test Suite VSU version 5.0.2
    Test Identification xcurses/wuncrtl 2
    Problem Summary TSD4U.00256 The test expects a different string for RS than the implementation produces.
    Problem Text
    This request applies to:

    /tset/CAPIxcurses/fwunctrl/fwunctrl1 2
    /tset/CAPIxcurses/functrl/functrl1 2

    In each case, the test verifies that the interface return control
    characters in "^X" notation by testing each control character against a
    sample character in that notation. But the test array includes:

    ...
    Test(u, "^]");
    u[0] = VSU_XC_RS;
    Test(u, "^~");
    u[0] = VSU_XC_US;
    Test(u, "^_");
    ...

    In our ASCII character set, VSU_XC_RS is "0x1e" and is respresented as
    "^^" rather than "^~".

    --

    This request was initially rejected as PG4U.00149. We disagree with the
    consultant's initial response:

    We recommend this request be refused.

    This test is verifying long standing historical practice, in which RS is
    represented as ^~. Changing this requirement would thus break backward
    compatability with existing implementations.

    Please note we have changed this from a TSD request to a PIN request as
    this is a specification issue, not a test issue.

    According to the specification for the "stty" utility, XCU5 p. 693, the
    <RS> control character is to be represented as "^^". Our implementation
    is correct.

    Please note we have changed this from a PIN request to a TSD request
    because it is a simple typo, not a specification issue.

    Test Output

    10|1537 /tset/CAPIxcurses/fwunctrl/fwunctrl1 06:15:38|TC Start, scenario
    ref 176
    -804
    15|1537 1.10 3|TCM Start
    400|1537 1 1 06:15:38|IC Start
    200|1537 1 06:15:38|TP Start
    520|1537 2 24327 1 1|SPEC1170TESTSUITE CASE 2
    520|1537 2 24327 1 2|When wc is a control character a call to wchar_t
    520|1537 2 24327 1 3|*wunctrl(cchar_t *wc) shall represent the wide
    520|1537 2 24327 1 4|character in ^X notation.
    520|1537 2 24329 1 1|TEST: Maps control characters correctly
    520|1537 2 24329 1 2|ERROR: wunctrl for 0x1e should be "^~" is "^^"
    220|1537 2 1 06:15:38|FAIL
    410|1537 2 1 06:15:38|IC End

    ---

    10|1357 /tset/CAPIxcurses/functrl/functrl1 05:13:58|TC Start, scenario ref
    176-6
    24
    15|1357 1.10 3|TCM Start
    400|1357 1 1 05:13:58|IC Start
    200|1357 1 05:13:58|TP Start
    520|1357 2 20628 1 1|SPEC1170TESTSUITE CASE 2
    520|1357 2 20628 1 2|When c is a control character a call to char
    520|1357 2 20628 1 3|*unctrl(chtype c) shall represent the character in ^X
    520|1357 2 20628 1 4|notation.
    520|1357 2 20630 1 1|TEST: Maps control characters correctly
    520|1357 2 20630 1 2|ERROR: unctrl(0x1e) should be '^~' is '^^'
    220|1357 2 1 05:13:58|FAIL
    410|1357 2 1 05:13:58|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We continue to disagree with the submitter.

    What the test suite expects is the behavior exhibited by every other
    implementation of curses we have ever seen. While this may be the result
    of a typo in the implementation of curses long ago, at this point it is
    venerable historical practice. Changing this does not seem necessary or
    desirable.

    We made the original request a PIN as, though we'd recommend against
    it, it opens the possibility of allowing both behaviors. As the submiter
    insists this is a TSD however, one or the other behavior must be chosen.
    It seems to us that the existing test requirement is the right choice as
    what the submitter suggests would cause all other curses implementations
    to be non-compliant.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    Please also note page 118 of System Interface Definitions, Issue 5
    which also appears to contradict the appeal. Thus we consider this
    suitable for an application for a Permanent Interpretation rather
    than a Test Suite Deficiency and recommend that it goes for
    a 14 day review.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    A TSD should be granted.

    The tests under review require that unctrl() and wunctrl() when
    called with the ASCII RS control character return "^~", but many other
    parts of the test suite (e.g. /tset/CAPIxcurses/faddstr/faddstr1{11})
    require that "^^" be recognized as the control character notation for
    RS. Furthermore, XBD's definition of control character notation (XBD5,
    P118) clearly requires "^^" (as does the XCU5 description of the stty
    utility (XCU5, P693) quoted by the submitter). As the test suite stands
    now, no implementation can ever conform because both forms are required
    exclusively by various parts of the test suite.

    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