Question about creating threads

[Viper187]

I was a little confused after reading the stuff on MSDN about CreateThread, ThreadProc etc.

1. When I create a thread, does it keep running over and over until ExitThread is called, or does returning any value kill it? The only one I've seen in action used a while(1) infinite loop and apparently returned when done or on error.

2. After calling CreateThread, can you call the ThreadProc(&lpParameter) to send it commands etc, just as if you were calling SendMessage on a callback for a window? I kind of wondered why that's a single pointer instead of allowing you to declare the ThreadProc with whatever vars you want it to receive (like window callbacks get HWND, MSG, LPARAM, WPARAM).

Basically, what I'd like to do is create a client thread for a winsock app to connect, if necessary reconnect, and handle sending/receiving socket data. It's a single connection that should stay open as long as the app is running, but if the other side is disconnected for some reason it needs to keep trying to reconnect. The reason for keeping it a separate thread is mainly that some of the data being transferred can take a long time. I suppose it's similar to writing an FTP app, but this is always connecting to the same place, automatically.

[scwizzo]

Threads do not continuously run. They are created and exit just like a function. I made a class to work with UDP sockets and mine creates a thread to receive data. While the thread is receiving data then do your other stuff. When the thread exits then call the thread again in a loop, or statement, or whatever you want. Basically have a loop calling the thread again when it exits.

I think the function I used to create my threads was _beginthread(). It's been a while since I looked at it.

[Viper187]

Thanks. I'll see what I can put together.

[Elysia]

ThreadProc is the function that the thread starts in. When the thread reaches the end of that function, it terminates.
And because the Thread API is C, and the thread API needs to take a function pointer to the thread to start execution in, it must be a pre-defined prototype.

And just to be clear - all the API that requires a function pointer requires a specific type of function. It must be the correct return type and the correct number of parameters and types. You cannot choose what they should take and not.

[Viper187]

Well, I came up with a method to suit my purpose for now.