diff options
Diffstat (limited to 'WinCE-PORT')
| -rw-r--r-- | WinCE-PORT | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -132,30 +132,30 @@ thread handle with GetCurrentThread() is sufficient, and it seems to work perfectly fine, so maybe DuplicateHandle was just plain useless to begin with ? ------------------------------------ -- In private.c, added some code at the beginning of _pthread_processInitialize -to detect the case of multiple calls to _pthread_processInitialize. +- In private.c, added some code at the beginning of ptw32_processInitialize +to detect the case of multiple calls to ptw32_processInitialize. Rational: In order to debug pthread-win32, it is easier to compile it as a regular library (it is not possible to debug DLL's on winCE). -In that case, the application must call _pthread_processInitialize() +In that case, the application must call ptw32_rocessInitialize() explicitely, to initialize pthread-win32. It is safer in this circumstance -to handle the case where _pthread_processInitialize() is called on +to handle the case where ptw32_processInitialize() is called on an already initialized library: int -_pthread_processInitialize (void) +ptw32_processInitialize (void) { - if (_pthread_processInitialized) { + if (ptw32_processInitialized) { /* * ignore if already initialized. this is useful for * programs that uses a non-dll pthread - * library. such programs must call _pthread_processInitialize() explicitely, + * library. such programs must call ptw32_processInitialize() explicitely, * since this initialization routine is automatically called only when * the dll is loaded. */ return TRUE; } - _pthread_processInitialized = TRUE; + ptw32_processInitialized = TRUE; [...] } |