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.135.22 with SMTP id j22mr3415253iod.117.1519301334197; Thu, 22 Feb 2018 04:08:54 -0800 (PST) X-Received: by 10.157.83.129 with SMTP id w1mr314566otg.2.1519301334065; Thu, 22 Feb 2018 04:08:54 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!weretis.net!feeder4.news.weretis.net!border2.nntp.ams1.giganews.com!nntp.giganews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!w142no197099ita.0!news-out.google.com!s63ni733itb.0!nntp.google.com!o66no196105ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 22 Feb 2018 04:08:53 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.240.212.129; posting-account=HnYppAoAAAASlROhcvCPTKUZJZdaMc9W NNTP-Posting-Host: 85.240.212.129 References: <503e3322-ee8e-4d6f-9aa5-e7b98f87e8f8@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <1d83a723-2668-493e-8b38-7cb9261eba70@googlegroups.com> Subject: Re: article on acces types and dynamic serialization in Ada (2003) From: guyclaude.burger@gmail.com Injection-Date: Thu, 22 Feb 2018 12:08:54 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Body-CRC: 3462733856 X-Received-Bytes: 2434 Xref: reader02.eternal-september.org comp.lang.ada:50546 Date: 2018-02-22T04:08:53-08:00 List-Id: >> what means exactly Some_access_type'Write(Stream1, Some_Pointer) ? > Bug, unless=20 > 2. Stream is used for communication inside the same program, e.g. the=20 pointer is simply marshaled.=20 "Bug", then why is it allowed... Considering access types as elementary typ= es also confuses me. First thing I learnt about them is you can't hardly ev= er assume they are simple addresses, or elementary. As for point 2, isn't i= t what I did in my first example ? I reset the file with mode IN, in immedi= ate enclosing block, 'Read it but got an erroneous memory access. There might be numerous ways around this linked data issue but having a san= e default implementation, as we already have defaults everywhere you can st= ill override. Maybe not enough requests, though it seems logical to me. I w= ouldn't want to bother with rewriting attributes if I want something as str= aightforward as "list references and identifiers, reconstruct by aliasing a= nd taking access here, use the stack there". Generics procedures should rea= lly be provided in the standard libraries for that. Not enough demands mayb= e ?