Saturday, August 10, 2019

Digest for comp.programming.threads@googlegroups.com - 3 updates in 3 topics

aminer68@gmail.com: Aug 09 02:34PM -0700

Hello,
 
Read again my final corrected post..
 
About parallel programming and concurrency..
 
Look at the following concurrency abstractions of microsoft:
 
https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.waitany?view=netframework-4.8
 
https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.waitall?view=netframework-4.8
 
 
I will soon implement waitany() and waitall() concurrency abstractions for Delphi and Freepascal, with the timeout in microseconds of course, and they will work with my efficient implementation of a Future, so you will be able to wait for one or many futures with waitany() and waitall().
 
And about task cancellation like in microsoft TPL, i think it is
not a good abstraction, because how do you know when you have to efficiently cancel a task or tasks ? so you are understanding that task cancellation is not a so efficient abstraction , so i will not implement it, because i think the waitany() and waitall() with the "timeout" in microseconds are good concurrency abstractions.
 
 
 
Thank you,
Amine Moulay Ramdane.
aminer68@gmail.com: Aug 09 02:29PM -0700

Hello,
 
 
About parallel programming and concurrency..
 
 
Look at the following concurrency abstractions of microsoft:
 
https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.waitany?view=netframework-4.8
 
https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.waitall?view=netframework-4.8
 
 
I will soon implement waitany() and waitall() concurrency abstractions for Delphi and Freepascal, with the timeout in microseconds of course, and they will work with my efficient implementation of a Future, so you will be able to wait for one or many futures with waitany() and waitall().
 
And about task canceletion like in microsoft TPL, i think it is
not a good abstraction, because how do you know when you have to efficiently cancel a task or tasks ? so you are understanding that task cancelation is not
a so efficient abstraction , so i will not implement it, because i think the waitany() and waitall() with the "timeout" in microseconds are good concurrency abstractions.
 
 
 
Thank you,
Amine Moulay Ramdane.
aminer68@gmail.com: Aug 09 02:25PM -0700

Hello,
 
 
About parallel programming and concurrency..
 
 
Look at the following concurrency abstractions of microsoft:
 
https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.waitany?view=netframework-4.8
 
https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.waitall?view=netframework-4.8
 
 
I will soon implement waitany() and waitall() concurrency abstractions for Delphi and Freepascal, with the timeout in microseconds of course, and they will work with my efficient implementation of a Future, so you can will be able to wait for many futures with waitany() and waitall().
 
And about task canceletion like in microsoft TPL, i think it is
not a good abstraction, because how do you know when you have to efficiently cancel a task or tasks ? so you are understanding that task cancelation is not
a so efficient abstraction , so i will not implement it, because i think the waitany() and waitall() with the "timeout" in microseconds are good concurrency abstractions.
 
 
 
Thank you,
Amine Moulay Ramdane.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.programming.threads+unsubscribe@googlegroups.com.

No comments: