Re: [Development] Using platform-native APIs for terminating QThreads

2016-09-02 Thread Marc Mutz
On Friday 02 September 2016 22:35:59 Thiago Macieira wrote: > However, the documentation from the ABI says that forced unwinds cannot be > stopped, so you can't swallow the exception even if you wanted to. Are you > sure that the application crashes when you pthread_exit() when >

Re: [Development] On deprecated APIs

2016-09-02 Thread Kevin Kofler
Marc Mutz wrote: > My porting guide for Q_FOREACH -> C++11 ranged for has created the > expected outcry from users. Well, at least I object to deprecating Q_FOREACH to begin with, even if you don't remove it. It's just the safer (no risk of accidental detaches, as long as you use Qt containers)

Re: [Development] Using platform-native APIs for terminating QThreads

2016-09-02 Thread Marc Mutz
On Friday 02 September 2016 12:32:48 Giuseppe D'Angelo wrote: > On some implementations (notably: glibc), pthread_exit is implemented by > throwing an exception, because it needs to run the pushed cleanup > handlers. The net result is that, with my change applied, pthread_exit > won't make the

[Development] Using platform-native APIs for terminating QThreads

2016-09-02 Thread Giuseppe D'Angelo
Howdy, I'm trying to introduce a change [1] which will make QThread invoke std::terminate in case an exception is thrown from the new thread (including, but not limited to: user's reimplementation of QThread::run; slots listening to the QThread::started / finished signals; custom event