Heinrich, > We really should always enable multithreading. > > 1) Enabling thread local storage makes no difference to single threaded > applications. So there is no reason to disable it. > > 2) A user has no chance to know if his DLL was compiled for > multithreading or not until his program fails. And he will not > understand why. > > 3) As David already pointed out distributions will not create multiple > versions of the library so their users simply will be lost. > > 4) There even isn't any documentation provided about this hidden switch. >
I don't mind. The only reason was to see how this option will work, because glpk is not designed for multi-threaded environments. Okay, I will add the test to configure.ac provided by Chris two weeks ago. Andrew Makhorin _______________________________________________ Help-glpk mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-glpk
