In our previous episode, Andrew Brunner said: > This seems like a discussion of semantics more than anything. In an > application thread if you say WAITFOR something then the app cannot > process messages b/c the execution is put on hold until WAITFOR > returns. This is normal behaviour, IMO. > > So if this is just an exercise, I really don't see a problem. What's > the issue you're trying to solve? Create a two thread system and have > the second thread WAITFOR the third thread to complete. Don't do this > with the main application thread for GUI apps. Service apps aren't > even an issue b/c it would just create a blocking condition - again > normal.
Or wrap such horrible threads (that hang long time, e.g. due to external programs) in an additional mechanism using an TEvent. TEvent has a waitfor with a timeout. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
