Stephen R. van den Berg wrote: >Stephen R. van den Berg wrote: >>How to work around this?
>So the simplest point of attack would be the json-parse function, >which I could ask not to create string references if it encounters integer >keys in a mapping (or force, by default, perhaps). That turned out to be a sort-of dead end, because it hands it off to Standards.JSON.decode(). Further investigation reveals that: <insert variable="q.m" index="2" /> actually uses a string to index the mapping, and therefore accesses the correct member. Problem solved. -- Stephen. Skiing beyond this point may result in death and/or loss of skiing privileges.
