I have thought about this, and here's how I would solve the problem.
Just make it a standard that a toolkit looks for an existing instance
of the keyword, and if it is in use, alter the keyword in a standardised
way.
Eg:
WIBBLE <ITEM>
tk9_WIBBLE <ITEM>
jms_WIBBLE <ITEM>
But that's just me.
HM! Well! What would happen to a standard program needing WOBBLE which was changed to WABBLE by this process?
Actually, both Qlib and Turbo are (or very soon will be) able to "include" the extensions really needed in the program so that they do not need to be LRESPRd at run time. Although this makes for longer programs compiling them might help to solve the problem of 72 keywords all called WYBBLE and all doing different things.
George
