On Thu, 16 Feb 2023 00:08:07 +0000, Seymour J Metz wrote: >Yes, that would break. That's one of the scenarios where you would need to use >the Linkage Editor. > That would have seemed to provide a compatibility argument against having made the change to a hierarchy. Was there any benefit in doing so?
Is Content Supervision guaranteed to continue to respect independence of those attributes? ________________________________________ From: Paul Gilmartin <0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Wednesday, February 15, 2023 6:59 PM > ... >Reentrant: You can invoke the module concurrently from multiple tasks and get >correct results. The code is responsible for any necessary serialization. > >Refreshable: The module gets correct results even if the OS replaces it with a >fresh copy in the middle of execution. 99% of the time refreshable modules are >read-only code. > >Originally marking as refreshable was independent of the other attributes, but >the Binder forces a hierarchy: > How much compatibility did this change break? Formerly, a module might have been marked refreshable because it was read-only code, but not reentrant because it relied merely on that property to serialize its access to an external resource. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
