Changes between Initial Version and Version 1 of Ticket #339


Ignore:
Timestamp:
05/29/2025 08:20:38 AM (14 months ago)
Author:
Gary Dixon
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #339 – Description

    initial v1  
    11When the get_equal_name_$check_equal_name_ entry point was added, the change did not add the check_equal_name_ onto the bound_library_1_ object segment, which would allow the new entry point to be referenced simply as check_equal_name_ (rather than get_equal_name_$check_equal_name_).
    22
    3 Also, the change did not add an include file with named constants defining the EQUAL_TYPE_xxx values that can be returned in the subroutine's code argument (in addition to the possible error_table_ values that argument also returns).  The get_equal_name_.info segment also does not document these EQUAL_TYPE_xxx values.  So any programmer that needs to use the check_equal_name_ entry point must: examine existing callers code to see how to use the results; or example get_equal_name_$check_equal_name_ entry point code to see what code values it returns.
     3Also, the change did not add an include file with named constants defining the EQUAL_TYPE_xxx values that can be returned in the subroutine's code argument (in addition to the possible error_table_ values that argument also returns).  The get_equal_name_.info segment also does not document these EQUAL_TYPE_xxx values.  So any programmer that needs to use the check_equal_name_ entry point must: examine existing callers code to see how to use the results; or examine get_equal_name_$check_equal_name_ entry point code to see what code values it returns.
    44
    55These omissions boost importance of this bug from an enhancement to a defect.