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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c9d5fc258548b22a X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!postnews.google.com!x4g2000prf.googlegroups.com!not-for-mail From: Edward Fish Newsgroups: comp.lang.ada Subject: Re: How do I write directly to a memory address? Date: Fri, 18 Feb 2011 20:21:42 -0800 (PST) Organization: http://groups.google.com Message-ID: References: <67063a5b-f588-45ea-bf22-ca4ba0196ee6@l11g2000yqb.googlegroups.com> <8e200ae9-51c7-4756-9d06-7b5dbc6eb85c@m27g2000prj.googlegroups.com> <4d5872d3$0$1707$882e7ee2@usenet-news.net> NNTP-Posting-Host: 174.28.187.177 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1298089302 30615 127.0.0.1 (19 Feb 2011 04:21:42 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Sat, 19 Feb 2011 04:21:42 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: x4g2000prf.googlegroups.com; posting-host=174.28.187.177; posting-account=IGEw6QoAAAChe8btAoGmJk0kqF3q3VLA User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13,gzip(gfe) Xref: g2news2.google.com comp.lang.ada:18412 Date: 2011-02-18T20:21:42-08:00 List-Id: On Feb 14, 4:25=A0pm, "Randy Brukardt" wrote: > "Hyman Rosen" wrote in message > > news:4d5872d3$0$1707$882e7ee2@usenet-news.net... > > > On 2/11/2011 11:47 PM, Edward Fish wrote: > >> But if you're using GNAT you may have noticed that it doesn't allow > >> a straight "For Data'Address Use 16#000B_8000#;" because GNAT > >> uses a private type and not a derivative of Universal_Integer. > > >> They recommend an implementation-dependent "to_Address" function, > >> but that would make things non-portable. > > > Portable to what? Other systems that also happen to have a two-segment > > address with a video frame buffer at 16#000B_8000#? Aren't you being a > > little pedantic here? > > There definitely are different degrees of portabaility. He's probably > thinking of "portable for the same target", that is, portable to another = Ada > implementation on the same target. > > That's not that uncommon of a goal. Claw, for example is intended to be a > portable interface to Windows, "portable" in the sense that it will work = on > all Ada 95 compilers that target Windows. This is something that has to b= e > baked in from the beginning, in that if you get in bad habits of dependin= g > on implementation-specific behavior, it can be very painful to work out f= rom > under them. You got it in one.