08867f7149
- calling the "call_completion" method unconditionally in finish_async (introduced by me) was wrong, because the thread may never be in an alertable wait state -> call it only if user completion function is present. - We need two constant "ops" objects, one with and one without call_completion method (the event field may NOT be used to determine whether the completion must be called or not). |
||
---|---|---|
.. | ||
messages | ||
nls | ||
tests | ||
.cvsignore | ||
Makefile.in | ||
comm.c | ||
comm.spec | ||
console.c | ||
debugger.c | ||
flatthunk.h | ||
format_msg.c | ||
kernel.rc | ||
kernel32.spec | ||
kernel_main.c | ||
krnl386.exe.spec | ||
locale_rc.rc | ||
stress.c | ||
stress.spec | ||
string.c | ||
sync.c | ||
system.spec | ||
thunk.c | ||
time.c | ||
toolhelp.c | ||
toolhelp.spec | ||
utthunk.c | ||
version.rc | ||
version16.rc | ||
win87em.c | ||
win87em.spec | ||
windebug.c | ||
windebug.spec | ||
wowthunk.c | ||
wprocs.spec |