#9 More on LOCAL-GLOBALS in v3

[Micke]

In order to see this bug, first correct the other V3 LOCAL-GLOBALS bug (described
in another ticket) by replacement of <GET .H .X> by <GET/B .H .X>.

In V3, if more than one LOCAL-GLOBAL object is added to a room (by using GLOBAL
in the definition) only the first such object per room is found by the parser.
In V5, all LOCAL-GLOBAL objects in a room are found as expected.