From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1b417df64012e6d3 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-03-17 17:42:41 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!cyclone2.usenetserver.com!usenetserver.com!newsfeed2.earthlink.net!newsfeed.earthlink.net!newsmaster1.prod.itd.earthlink.net!newsread2.prod.itd.earthlink.net.POSTED!not-for-mail Message-ID: <3C95460D.4B2419D0@acm.org> From: Jeffrey Carter X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: tasks, protected types and entries References: <%12l8.9656$%_6.1717935@news11-gui.server.ntli.net> <3C94F235.80C7166A@adaworks.com> <1f8l8.12464$yb3.3172535409@newssvr11.news.prodigy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 18 Mar 2002 01:42:44 GMT NNTP-Posting-Host: 209.86.208.35 X-Complaints-To: abuse@earthlink.net X-Trace: newsread2.prod.itd.earthlink.net 1016415764 209.86.208.35 (Sun, 17 Mar 2002 17:42:44 PST) NNTP-Posting-Date: Sun, 17 Mar 2002 17:42:44 PST Organization: EarthLink Inc. -- http://www.EarthLink.net X-Received-Date: Sun, 17 Mar 2002 17:42:40 PST (newsmaster1.prod.itd.earthlink.net) Xref: archiver1.google.com comp.lang.ada:21388 Date: 2002-03-18T01:42:44+00:00 List-Id: Pat Rogers wrote: > > "Richard Riehle" wrote in message > news:3C94F235.80C7166A@adaworks.com... > > "chris.danx" wrote: > > > > > What is the difference between an entry and a procedure? > > > > This is one of the most important and least often address issue > > in Ada. In my classroom, after we have started our unit on > > tasking, I have my students recite, in unison, > > > > "An entry has a queue." > > Unless the Real-Time Annex is used, with the Ceiling_Locking policy. Then there > is no need for a queue. This is incorrect. Even with ceiling locking, an entry needs a queue. If the entry barrier is false, ceiling locking does not prevent multiple tasks from calling the same entry. -- Jeff Carter "Go and boil your bottoms." Monty Python & the Holy Grail