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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Simon Clubley Newsgroups: comp.lang.ada Subject: Re: Comments requested for a couple of Ada-Comments submissions Date: Fri, 11 Jul 2014 07:05:36 +0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: Injection-Date: Fri, 11 Jul 2014 07:05:36 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="e458ff8b81bc0c159989eb0e36c6e372"; logging-data="4981"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+LoaTZZEEhcwmwsWPMJfxr3ZAkTo43xQU=" User-Agent: slrn/0.9.8.1 (VMS/Multinet) Cancel-Lock: sha1:w7suMNFR8AQE/SkDsSJdYqMVj3s= Xref: news.eternal-september.org comp.lang.ada:20865 Date: 2014-07-11T07:05:36+00:00 List-Id: On 2014-07-11, Randy Brukardt wrote: > > I think you ought to add something on this line to your submission; the > critical point (the problem, as always) is buried that the very end of your > question. Here, the problem is that accessing a device register piecemeal > does not work, and there should be a way in Ada to prevent such accesses. If > the existing rules don't have that effect, then we need some mechanism to > ensure proper access. > > So, I'd suggest putting the problem first (as in an AI), the question about > the existing rules second, and then (optionally) a possible solution if the > existing behavior is confirmed. > Thanks Randy. I'll revise it this weekend and post an updated version for comments before submission. Simon. -- Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP Microsoft: Bringing you 1980s technology to a 21st century world