On 95 Jan 02 at 13:12, Edwin Groothuis of 2:284/205.1 wrote:

 EG> I have a very serious problem...

No, you don't.  :)

 EG> In the redbook of os/2 v2.0 there is the following text:

 EG> ``The _beginthread() function provided by the C compiler 
 EG> should be used to create secondary threads that will contain 
 EG> object windows or that contain code which calls C run-time 
 EG> library functions. This function maintains certain internal 
 EG> C library control data that is, by default, not maintained 
 EG> by the DosCreateThread() function.''

 EG> Easy... but how about the following text:

 EG> ``The DosCreateThread() function provided by OS/2 may be 
 EG> used to create secondary threads that will not contain 
 EG> object windows and that do not call C run-time library 
 EG> functions.''

 EG> I understand the part of the object windows, but what do 
 EG> they mean with the ``C run-time library functions?''

"C run-time library functions" are functions in the C run-time library.

Here's how it works.  The _beginthread() call does some stuff, and then
calls DosCreateThread().  If you don't need that other stuff done first,
then you can just call DosCreateThread() directly.

What is that other stuff for?  If you are going to call any functions which
are part of the C run-time library that comes with the compiler, such as
malloc() or strcpy(), then you need to have that other stuff done and you
must use _beginthread().

Considering the amount of overhead involved and the fact that creating
threads is not something you should be doing a lot of, it is probably good
practice to always use _beginthread() and never call DosCreateThread()
directly.
 
-- Mike
 

--- Msgedsq/2 2.2e