Weird

After takin' a swig o' grog, mlw belched out this bit o' wisdom:

My code indicates that the worst case is significantly worse. (Though that case would be uncommon in most applications.)

Having the thread take care of both creation and deletion also seems to be a good benefit, to me.

But I do want to write some code to have the main thread to the copying, and each thread take care of deleting its copy, while making sure that nothing is left hanging if the thread is prematurely terminated. So much to learn!

Which platforms?

Sure it is. No call to free() necessary. Ignoring the locking

Only if you create an errant pointer. How else are you going to see another function's auto variables?

Such as? I'd like to know about them, and how they are used in real applications. Specific data is difficult to track down, and I could use your help, mlw.

Thanks! My main concern at the moment is getting thread creation as fast and painless (to the coder) as possible.

I see. I'm still (after a couple of years) working on mastering the

-- Q: Why does a GNU-Linux user compile his kernel? A: Because he can.