Someday we will actually write the contents for the wine/documentation/patches.sgml
file and this question will be easier to answer :)
Here is some draft content for the file that I would add if only I felt I were
competent in SGML: Amend away folks!
Patch Format
Your patch
This Wine critical section tracking patch is based on a patch Jeremy White (of
CodeWeavers) wrote for the Corel branch back in February. I have warped and extended
if for the current WineHq head
revision.
The WineHQ head revision seems to use a LOT more critsects than the current Corel
"Dimitrie O. Paun" [EMAIL PROTECTED] writes:
Now, AFAICS, Xlib calls are thread
safe from the glibc point of view, but
until the above mentioned patch got
applied, they were not from Wine POV.
However, now that we play nice with
glibc locking, shouldn't the Xlib
calls become thread safe
From: "Alexandre Julliard" [EMAIL PROTECTED]
Yes, if you only consider systems using a recent glibc and a
thread-safe Xlib.
True. But, I guess, we can assume that for Linux-based system,
right?
I doubt you will have much success with a proposal
that we should stop supporting all other
Continuing in my efforts to get MOD4WIN working, I have come across the
following problem. Its a 16bit application and it calls waveOutReset
while holding the Win16Mutex (SysLevel 1). Wine attempts to send a
notify message back about this. However, the notify gets sent from a
different thread.
