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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0800 Actions

    Problem Report Number 0800
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0315
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1996-11-19 08:00
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.6
    Test Identification POSIX.upe/ex 1005
    Problem Summary TSD4C.00196 This test may fail on all implementations.
    Problem Text
    This test fails on implementations that use spaces instead of tabs for
    indentation.

    The test case calls 'ex' on an input file with the following commands:

    set lisp
    set autoindent
    a
    (defn alt
    (i).
    ( + 1 2))
    .
    x

    It then calls 'grep -E' to verify the content of the file, expecting
    lines that begins with two spaces followed by one or more tab/space, or
    with a tab followed by zero or more tab/space. The following comment
    is from the test case:

    # ERE describing the expected suitably indented output
    # begins with 2 spaces followed by at least one tab/space or
    # with a tab followed by optional tab/spaces
    # "^(\s\s[\t\s]+|\t[\t\s]*)"

    In fact, this comment describes the test incorrectly: the actual
    pattern supplied to 'grep -E' expects two spaces followed by one or
    more tab (it's missing a space). In other words, the pattern supplied
    to grep is

    "^(\s\s[\t]+|\t[\t\s]*)"

    However, both the comment and the test are wrong in that they specify a
    much stronger test than the XPG4 specification. XPG4 does not specify
    the format for indentation. The test case failed because our
    implementation uses spaces (with no tabs) for indentation.

    Note: See also waiver TSD4C.00106 for related information.
    Test Output
    Assertion #1005 (C): Test lisp option on set option autoind
    <LC> ent
    '(i).' wasn't found in standard output
    '( + 1 2))' wasn't found in standard output

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We agree this is a test suite deficiency in the test
    suite version(s) listed.

    The submitter is correct that the test may fail on all
    implementations as written. But we believe this is a result of
    the way the test is written, not because of the argument against
    the necessity for tabs that the submitter makes.

    The VSC ex lisp option states

    lisp
    Autoindent mode and...

    The VSC ex autoindent option states

    autoindent, ai
    If autoindent is set, each line in the input mode will be
    indented (using first as many tab characters as possible,,,

    Thus the implementation must use tabs in preference to spaces
    wherever possible.

    We suspect that the submitters application fails to meet the
    requirements of the spec, but the test is not written properly so
    it is impossible to tell for sure. If we are correct the submitter's
    implementation will fail the rewritten test in the next release.

    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