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

The Open Brand -- Problem Reporting and Interpretations System


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


Report 0684 Actions


    Problem Report Number 0684
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0077
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1997-07-07 08:00
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.5
    Test Identification POSIX.upe/ex 379
    Specification Commands and Utilities Issue 4 Version 2
    Location in Spec See Problem Text
    Problem Summary PIN4C.00037 This test may fail on implementations that begin with the last line instead of the first. Although POSIX.2 interpretation #64 reaffirms the behavior, the POSIX.2b draft reinstates the historic behavior.
    Problem Text
    This test may fail on implementations that begin with the last line
    instead of the first. Although POSIX.2 interpretation #64 reaffirms
    the behavior, the POSIX.2b draft reinstates the historic behavior.

    The IEEE Std 1003.2-1992/INT December 1994 edition, interpretation 64
    part 9 describes a difference between the POSIX 1003.2 definitions
    and historical behaviour as follows

    "(9) Commands Descriptions (5.10.7.2, page 523, line 1309). Historically,
    if both a count and range were specified, the offset was from the
    last address not the first. The offset in the case was inclusive,
    therefore :2, 5c7 changes line 5 and six others..."

    And the outcome was that this is a defect in the standard:

    "(9) The standard states the behaviour for ranges and counts in ex,
    and conforming implementations shall conform to this. However,
    concerns have been raised about this, which are being raised to
    the sponsor."


    Looking in detail at the test output, the first diff section is identical
    to TIN4C.00024, but the second diff section is not.

    Test 379 part 2 fails as follows on our implementation with:

    *** ex_data_2
    --- ex_exp_2
    ***************
    *** 1,5 ****
    12
    abc
    ! abc abc
    def
    ! 012 abc abc
    --- 1,5 ----
    12
    abc
    ! 012 abc
    def
    ! abc abc abc


    Whereas TIN4C.00024 granted a waiver for this as

    *** ex_data_2
    --- ex_exp_2
    ***************
    *** 1,5 ****
    12
    abc
    ! abc abc
    def
    abc abc abc
    --- 1,5 ----
    12
    abc
    ! 012 abc
    def
    abc abc abc


    The test prepares a buffer

    abc
    abc
    abc abc abc
    def
    abc abc abc

    and then executes the following ex commands

    1
    s/abc/012/
    /abc /,$&2
    w
    q
    EOF


    This says go to line 1, and then change the first abc to 012, so the
    buffer is then

    12
    abc
    abc abc abc
    def
    abc abc abc

    The next command says for the range of pattern /abc / to $, run
    the last substitue command, historically the actual lines have been
    the last line + count-1 lines, as stated in the interpretation request,
    we therefore end up with

    12
    abc
    abc abc abc
    def
    012 abc abc


    Test Output
    ***********************************************************************
    /tset/POSIX.upe/ex/ex_07.ex 1 Failed


    Test Information:
    Assertion #379 (C): specification of ex "range & count" com
    <LC> mand
    Note: The behavior associated with this assertion is expec
    <LC> ted
    to change in a future revision of POSIX.2.
    diff of "ex_data_1" and "ex_exp_1":
    *** ex_data_1 Wed Dec 6 00:39:09 1995
    --- ex_exp_1 Wed Dec 6 00:39:09 1995
    ***************
    *** 1,5 ****
    012 abc
    - abc
    - abc
    - def
    12
    --- 1,5 ----
    012 abc
    12
    + 012
    + def
    + abc
    Command failed: 'cmp_show ex_data_1 ex_exp_1'
    diff of "ex_data_2" and "ex_exp_2":
    *** ex_data_2 Wed Dec 6 00:39:11 1995
    --- ex_exp_2 Wed Dec 6 00:39:11 1995
    ***************
    *** 1,5 ****
    12
    abc
    ! abc abc
    def
    ! 012 abc abc
    --- 1,5 ----
    12
    abc
    ! 012 abc
    def
    ! abc abc abc
    Command failed: 'cmp_show ex_data_2 ex_exp_2'

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



    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    Anticipating acceptance of the completely rewritten ex specification
    in POSIX 2003.2b/D11 and the eventual alignment of the tests with it
    a temporary interpretation is recommended.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Permanent Interpretation (PIN)
    Review Conclusion
    A Permanent Interpretation is granted.

    Problem Reporting System Options:

     

    Back   


Contact the Certification Authority