On 2015-01-16 12:28 AM, Tony Lezard wrote: > Win32 threading is broken? Do you mean that it's being used incorrectly in > the gnubg code or are you claiming it's fundamentally flawed in itself, > which is a mighty big statement to make.
Sorry about the ambiguity. The Win32 subsystem of the OS functions correctly. Our usage of it when using that API directly is flawed. Our code that uses GLIB Threads works properly. GLIB ultimately calls the same Win32 threading API under the hood. Our code is littered with ifdefs to deal with either choice and I did note a couple of differences that are likely related to why they work differently. Maintaining multiple code paths already seems to be an issue. I am just suggesting we eliminate one of the code paths if it doesn't really work and may be of limited value in keeping. -- Michael Petch GNU Backgammon Maintainer / Developer OpenPGP FingerPrint=D81C 6A0D 987E 7DA5 3219 6715 466A 2ACE 5CAE 3304 _______________________________________________ Bug-gnubg mailing list Bug-gnubg@gnu.org https://lists.gnu.org/mailman/listinfo/bug-gnubg
