TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
Blue Herring <[log in to unmask]>
Date:
Thu, 22 Apr 1999 06:30:39 -0700
Content-Type:
text/plain; charset=us-ascii
MIME-Version:
1.0
Reply-To:
Blue Herring <[log in to unmask]>
Parts/Attachments:
text/plain (27 lines)
I have an issue I would like to hear some feedback on
if I could.  Ada 95 introduced protected types, and
information on the new concurrent standard, which I
heard was the thing most changed from 83, is difficult
(at least has been for me) to get much detail on.  One
issue I had, was that I read somewhere that protected
procedures and so forth, when executed, will run until
completed, and not be interrupted by time slicing and
so forth.  This certainly does the job, but as a
learned friend of mine pointed out, Ada protected
types are meant to passively guard critical section
data, but time slicing in the middle of execution
would be fine, as long as mutual exclusion was
maintained.  Is there a specific way this happens in
the 95 standard, or is it implementation dependent?

I'm also curious if there is a compiler out there
which does enforce consistant time slicing, since Gnat
supposedly doesn't.

-Matt Goulet
     aka The Mildly Infamous Blue Herring

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

ATOM RSS1 RSS2