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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1769 Actions

    Problem Report Number 1769
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0215
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1998-02-12 08:00
    Product Standard Window System Application Interface V2
    Certification Program The Open Brand certification program
    Test Suite VSW version 5.0.0
    Test Identification Xt11/tcalcnvtr 10
    Specification Window Management (X11R5): X Toolkit Intrinsics
    Location in Spec See Problem Text
    Problem Summary PIN4W.00022 This IR maintains that XtCallConverter need not examine the conversion cache if the converter was not previously registered.
    Problem Text
    According to the refence code of Xopen(cf Xt/Convert.c)
    if a converter has not been registered with
    XtSetTypeConverter, XtAppAddConverter or XtAppSetTypeConverter
    it is not placed converterTable.

    XtCallConverte checks if the Converter
    is in converterTable (GetConverterEntry). If not
    it is called again; that is no cached value is used.

    This test cannot expect XtCVT1a_StringToChar to be
    called only once since none of the above mentioned
    three calls where made.
    Test Output
    SECTION: Xt11

    TEST CASE: XtCallConverter

    TEST PURPOSE #10
    520|2668 10 00017638 1 1|VSW5TESTSUITE PURPOSE 10
    520|2668 10 00017638 1 2|Assertion XtCallConverter-10.(A)
    When the type converter converter has not been registered
    for the application context associated with display and the
    converter has not been previously called with the specified
    arguments a call to Boolean XtCallConverter(display,
    converter, args, num_args, from, to_in_out,
    cache_ref_return) shall call the converter, enter the result
    into the conversion cache, store the converted value into
    the location specified by to_in_out->addr, and return what
    the converter returns.
    PREP: Initialize toolkit, Open display and Create topLevel root widget
    PREP: Create windows for widgets and map them
    TEST: Invoke resource converter XtCVT1a_StringToChar
    TEST: Return value
    TEST: Procedure XtCVT1a_StringToChar was invoked
    TEST: Result returned
    TEST: Re-Invoke resource converter with same values
    TEST: Return value
    TEST: Procedure XtCVT1a_StringToChar was not invoked
    ERROR: Expected XtCVT1a_StringToChar invoked count of 1, Received 2
    TEST: Result returned
    FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    Section 11.6.5 of the X/Open X Toolkit Intrinsics specification is
    the normative reference regarding this issue. It states that

    The XtCallConverter function looks up the specified type
    converter in the application context associated with the display
    and, if the converter was not registered ... looks in the
    conversion cache to see if this conversion procedure has been
    called with the specified conversion arguments. If so it checks
    the success of the prior call and ... copies the information
    stored in the cache.

    So the conversion cache is examined whether the converter is registered
    or not. If the arguments match and the previous call succeeded, which
    is true in the test being discussed, then the cached value should be
    used. The converter should not be called twice.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    This is a known problem in the reference implementation
    and in line with our recent decision to align with
    existing technology we are granting a Permanent Interpretation.
    The problem is fixed in R6.4.

    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