In our previous episode, Andrew Brunner said: > > IMO - it may be smarter to develop of a new threading paradigm. A HPC > threading system that addresses issues with waitfor/suspend/resume and > resolve them for *nix/windows/mac but do so knowing that there are > most likely tens of thousands of threads running.
> TThread object has been implemented (under *nix) with redundant > barriers in creation, suspend, and resume features. This redundancy > makes for slow thread creation times and as such is not ideal as is. What is exactly the problem? A problem that a 5 second thread pool implementation can't solve? _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
