Improve or warn about ReceiveWait and creating task with function about omnithreadlibrary HOT 4 OPEN

Good catch! I think this should be considered a bug and should be fixed.

from omnithreadlibrary.

BTW, your approach looks a bit weird to me. Why do you call the Execute if you then immediately check if you can run it at all? Can't you just call Run without a parameter and then do 'task.Invoke(Execute)' when you actually need it?

from omnithreadlibrary.

I don't want to make the demo too complex ;)

Just add the IOmniThreadPool and set MaxExecuting := 1. Followed by:

CreateTask(TMyOmniWorker.Create(True)).MonitorWith(FOmniEM).
  Schedule(FThreadPool).Invoke(@TMyOmniWorker.Execute)

Same result.
Now, the tasks are inside the queue and at the time a specific task is able to run (because all previous tasks have been finished), the time has passed and the task caller is maybe gone and this specific task is unnecessary to be done.

http://geskill.bplaced.net/hp/other/OmniWorkerTestwithMonitorandThreadPool.zip

PS: Now even more internal calls have to be redirected from ReceiveWait ^_^

from omnithreadlibrary.

OK, that is a sensible argument.

from omnithreadlibrary.