Changes between Initial Version and Version 1 of Ticket #336


Ignore:
Timestamp:
06/03/2024 12:19:45 PM (2 years ago)
Author:
Gary Dixon
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #336 – Description

    initial v1  
    11Most bound objects permit debugging using unbound components from the bound object (compiled with symbol tables, changes, etc). 
    22
    3 However the ssu_invocation_.pl1 component of bound_ssu_ takes precautions to ensure that any unbound components referenced as links by bound_ssu_ (like the ssu_et_ error table, ssu_request_tables_ and ssu_requests_ built-in requests) are found within the bound_ssu_ bound object containing ssu_invocation_.  The switch_ssu_refnames internal procedure implements this precaution.
     3However the ssu_invocation_.pl1 component of bound_ssu_ takes precautions to ensure that any unbound components referenced as links by bound_ssu_ (like the ssu_et_ error table values, ssu_request_tables_ entries and ssu_requests_ built-in request subroutines) are found within the bound_ssu_ bound object containing the running ssu_invocation_ component.  The switch_ssu_refnames internal procedure implements this precaution.
    44
    55The precaution is reasonable when running ssu_ from the bound_ssu_ bound object to ensure that all ssu_ components see the expected component versions (those in the bound_ssu_ segment).  Without such precaution, any developer version of ssu_et_, ssu_request_tables_ or ssu_requests_ found by the user's linker search paths might be invoked unexpectedly when running the installed bound_ssu_.