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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.15.143 with SMTP id 15mr36369978iop.15.1456266307730; Tue, 23 Feb 2016 14:25:07 -0800 (PST) X-Received: by 10.182.88.134 with SMTP id bg6mr364500obb.3.1456266307643; Tue, 23 Feb 2016 14:25:07 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!peer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!y89no3546216qge.0!news-out.google.com!h70ni679qge.0!nntp.google.com!w104no2890325qge.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 23 Feb 2016 14:25:07 -0800 (PST) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=138.162.0.42; posting-account=9yqilwkAAAAlbxojEc6DW1OEOsACipCN NNTP-Posting-Host: 138.162.0.42 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <7663896a-a15e-47fd-8c7e-54a1c20d8d0f@googlegroups.com> Subject: Protected Objects and Interrupt Handlers From: Jere Injection-Date: Tue, 23 Feb 2016 22:25:07 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 1510 X-Received-Body-CRC: 3690038260 Xref: news.eternal-september.org comp.lang.ada:29594 Date: 2016-02-23T14:25:07-08:00 List-Id: This is more of a curiosity, but I have noticed that a lot of embedded Ada = examples that I run across use a protected type object to wrap the ISR for = a particular interrupt. I was wondering why this is? Why not just use a n= ormal Ada procedure for an interrupt? I can understand using a protected o= bject to handle procedures used by different tasks, but an ISR isn't a task= per say. So how do Ada's protected type object and procedure implementati= ons work with interrupts?