TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Programming Language Advocacy (83 & 95)" <[log in to unmask]>
Date: Thu, 17 Mar 2005 11:39:43 +0100
Content-Transfer-Encoding: quoted-printable
From: Colin Paul Gloster <[log in to unmask]>
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Parts/Attachments: text/plain (17 lines)
Stephen Leake <[log in to unmask]> said:
"[..]

[..] "task"
is Ada's name for "thread"; it is helpful in this context to
distinguish between the two, since they have somewhat different
semantics. Each vendor typically needs to add some "glue" on top of
the underlying thread implementation to make it meet the "task"
semantics. 

[..]"

Actually "task" is Ada's term for "process" not "thread". A process could
have a number of subprocesses called threads which share data without mutual
exclusion from the same process, like in POSIX or pthreads but thankfully
not Ada.

ATOM RSS1 RSS2