> I'm running behind so someone may have already mentioned this, but Shmuel > gave a sample of a refreshable but non-reentrant code. The code did not > modify itself; it modified something else sacred - the CVT as I recall. > The code could be refreshed at any time without altering its behavior, but > in order to be reentrant/reenterable (in it's prior meaning) the code had > to include serialization.
I don't think he did. If you widen the definition of reentrant to include all external data then all bets are off. I would argue that such a program is just badly designed no matter what purported attributes it has. The system provides well-behaved mechanisms for well-behaved programs. It is a bit much to expect miracles when the program violates serialization rules. CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
