Liste des Groupes | Revenir à cl ada |
"Niklas Holsti" <niklas.holsti@tidorum.invalid> wrote in messageOk, I understand. In that case, what "parallel" adds to the current tasking feature is an easy way to create a largish and perhaps dynamically defined number of concurrent threads from a "parallel" loop, where the threads are automatically created when the loop is started and automatically "joined" and destroyed when the loop completes.
news:lk3fsvF7aaaU1@mid.individual.net...
...I disagree with Randy's view that tasks and "parallel" are muchI was (of course) presuming that "tasklets" would get those capabilities if
overlapping. Tasks are able to communicate with each other, but AIUI
parallel tasklets are not meant to do that, and may not be able to do
that. Tasks can have different priorities; tasklets cannot.
they were to replace tasks. That's what I meant about "suspension", which is
not currently allowed for threads in Ada (parallel code is not allowed to
call potentially blocking operations). If that was changed, then all forms
of existing task communication would be allowed.
I'm less certain about the value of priorities, most of the time, they don'tPriorities (or the equivalent, such as deadlines) are absolutely required for real-time systems where there are fewer cores than concurrent/parallel activities so that the system has to schedule more than one such activity on one core.
help writing correct Ada code. (You still need all of the protections
against race conditions and the like.) I do realize that they are a natural
way to express constraints on a program. So I admit I don't know in this
area, in particular if there are things that priorities are truly required
for.
Les messages affichés proviennent d'usenet.