Jonathan Wakely wrote:
> there's a race on the memory allocation in ResUse::field_types(int).
I'm pretty sure the whole create-on-demand strategy used with FieldNames
and FieldTypes is a crock, but I haven't put in the time to prove it
yet. Aside from the thread safety implications, it means you have to
test the pointer all the time to be sure it's allocated, and if not,
repeat the allocation code inline. Bleh.
At *minimum* we need to hide the pointer behind an accessor that wraps
all this. If we can just allocate it on object creation without
horrible consequences, so much the better.