> It's more a case of it being a dangerous solution. There is every
> chance the thread will run before the object is constructed on a
> multi-core system, or even a single code one if the new thread gets to
> run first.

I will repeat myself once more, the code I posted is in NO WAY complete,
so do not assume it to be useable as-is. I just took the essence of the
way I do things so that Mr. JackC can use with ease.