On Tue, Jul 17, 2012 at 1:01 PM, Dmitry Karasik <[email protected]> wrote: > > Prima by design is not thread-safe because there are so many global > state variables, and even if it would be possible to circumvent the problem > above, it requires a huge effort to go through all code to make sure it > is thread safe. Subjectively, I don't justify that effort, because it looks > to me that people mostly call GUI from other threads to reflect state of > a lenghty calculation or a similar, and that can be done by some other > IPC method, where thread2 signals a condition and thread1 picks it up > and calls a Prima method. > > Well anyway I'm willing to cooperate if there are volunteers that want > to try this risky enterprise, but personally I don't see much interest or > benefit in this.
+1 I see all downside and no upside to this work. Almost every GUI toolkit I know has a "favored thread" for the GUI and expect the users to do their own locking, synchronization, and communication if they want to use multiple threads. --Chris _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
