cvs commit: src/include stdio.h src/lib/libc/gen _pthread_stubs.c src/lib/libc/stdio _flock_stub.c asprintf.c findfp.c fseek.c local.h refill.c snprintf.c sprintf.c sscanf.c ungetc.c vasprintf.c vfprintf.c vsnprintf.c vsprintf.c vsscanf.c
joerg at britannica.bec.de
Tue May 10 04:27:15 PDT 2005
On Tue, May 10, 2005 at 06:27:07AM +0800, davidxu wrote:
> We already did the optimizations by using macro FILELOCK In
> libc_private.h. Another reason to not use recursive mutex is that
> default mutex is not recursive, and dynamically creating it have
The first is fine, but not a reason to avoid recursive mutexes.
The second is strange, we have to create the mutex dynamically
anyway. This needs to be done at one point or another anyway,
even for the case of a normal mutex. Question is of course, which
is the best time to initialise it.
More information about the Commits