summaryrefslogtreecommitdiff
path: root/WinCE-PORT
diff options
context:
space:
mode:
authorrpj <rpj>2000-08-17 10:18:36 +0000
committerrpj <rpj>2000-08-17 10:18:36 +0000
commita366b6d8c2e6debf247c82af3d41aa2483711c52 (patch)
treee2a2f6785897a8789f88403e99d4f03dce301607 /WinCE-PORT
parent951895c3aa196e90d4a5ecefe337d8773b8d33b7 (diff)
2000-08-17 Ross Johnson <rpj@special.ise.canberra.edu.au>
* All applicable: Change _pthread_ prefix to ptw32_ prefix to remove leading underscores from private library identifiers (single and double leading underscores are reserved in the ANSI C standard for compiler implementations).
Diffstat (limited to 'WinCE-PORT')
-rw-r--r--WinCE-PORT16
1 files changed, 8 insertions, 8 deletions
diff --git a/WinCE-PORT b/WinCE-PORT
index 9de284d..80b3bd3 100644
--- a/WinCE-PORT
+++ b/WinCE-PORT
@@ -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;
[...]
}