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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0717 Actions

    Problem Report Number 0717
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0110
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1995-06-16 08:00
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.3
    Test Identification XOPEN.cmd/m4 80
    Specification Commands and Utilities Issue 4 Version 2
    Location in Spec See Problem Text
    Problem Summary PIN4C.00004 m4 writes to stderr - spec is incorrect.
    Problem Text
    The X/Open Specification, Commands and Utilities Issue 4, Version 2 states:
    "The dumpdef macro writes the defined text for each of the macros specified as
    arguments, or, if no arguments are specified, for all macros."

    In the STDOUT section for m4, the X/Open Specification states:
    "The standard output is the same as the input files, after being processed for
    macro expansion."

    In the STDERR section for m4, the X/Open Specification states:
    "Used to display strings with the errprint macro, macro tracing enabled by the
    traceon macro, or for diagnostic messages."

    Assertion 80 states:
    "When dumpdef is invoked with no arguments, then it prints the current names
    and definitions for all defined macros."

    The VSC test expects the defined text for the macros to be written to stdout.
    Because the STDERR section of the X/Open Specification does not mention
    dumpdef, VSC correctly tests the assertion.
    XCU4 tried to expand the SVID-like description in XCU3 into a POSIX.2-like
    description in XCU4. However, historic System V practise is that the defined
    text for the macros is written to stderr. The X/Open Specification
    should state that dumpdef writes the defined text for the macros to stderr,
    because it was not intended that m4 be changed from historic practise.
    Test Output
    Assertion #80 (C):
    checking for ''
    checking for 'alpha'
    macro 'alpha' definition not output.
    checking for 'beta'
    macro 'beta' definition not output.
    checking for 'gamma'
    macro 'gamma' definition not output.
    checking for ''
    Assertion Result: FAIL

    This assertion is tested by executing "m4 file.in", where file.in contains:
    define(alpha,First macro.)dnl
    define(beta,Second macro.)dnl
    define(gamma,Yet another macro definition.)dnl
    80_START
    dumpdef
    80_END

    The following is written to stdout:
    80_START

    80_END

    The defined text for the macros is written to stderr:
    m4wrap: <m4wrap>
    m4exit: <m4exit>
    beta: Second macro.
    defn: <defn>
    decr: <decr>
    define: <define>
    eval: <eval>
    incr: <incr>
    ifelse: <ifelse>
    popdef: <popdef>
    traceoff: <traceoff>
    undefine: <undefine>
    unix:
    maketemp: <maketemp>
    divert: <divert>
    sinclude: <sinclude>
    syscmd: <syscmd>
    divnum: <divnum>
    sysval: <sysval>
    substr: <substr>
    undivert: <undivert>
    translit: <translit>
    errprint: <errprint>
    ifdef: <ifdef>
    gamma: Yet another macro definition.
    dnl: <dnl>
    alpha: First macro.
    len: <len>
    changecom: <changecom>
    index: <index>
    include: <include>
    shift: <shift>
    dumpdef: <dumpdef>
    traceon: <traceon>
    pushdef: <pushdef>
    changequote: <changequote>

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The XPG4 version of the m4 manual page does not specify where the output of
    the dumpdef macro should be sent. The claim in the waiver request that
    historic practise indicates that this should be sent to stdout should be
    verified by polling the Base Working Group. The most probable outcome is
    that the requestor is correct, the specification and test suite require
    modification, and that the waiver should be granted. It is recommended that
    the default action should be to grant a Permanent Interpretation.

    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