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 2002:a24:fa85:: with SMTP id v127-v6mr458954ith.11.1528757303144; Mon, 11 Jun 2018 15:48:23 -0700 (PDT) X-Received: by 2002:a9d:6218:: with SMTP id g24-v6mr888144otj.4.1528757303031; Mon, 11 Jun 2018 15:48:23 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!1.eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!85.12.16.68.MISMATCH!peer01.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!u78-v6no3624581itb.0!news-out.google.com!c20-v6ni4006itc.0!nntp.google.com!u78-v6no3624576itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 11 Jun 2018 15:48:22 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=76.113.16.86; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 76.113.16.86 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: why access parameter in stream attributes to begin with, instead of in or in/out ? From: Shark8 Injection-Date: Mon, 11 Jun 2018 22:48:23 +0000 Content-Type: text/plain; charset="UTF-8" X-Received-Bytes: 1942 X-Received-Body-CRC: 3578457793 Xref: reader02.eternal-september.org comp.lang.ada:53056 Date: 2018-06-11T15:48:22-07:00 List-Id: On Monday, June 11, 2018 at 3:49:28 PM UTC-6, Mehdi Saada wrote: > Hi. > > I wondered why in Ichibiah's design, in the beginning, stream have been made to work with access types/access parameters ? Hard to say; his design [Ada83] didn't have streams. > I could have imagined that the attributes would work with a in/out stream parameter, and stream(blabla) would give an object of stream type. > I don't know if storing streams' access values for later use is common, one would just have to add .all when appropriate... Good questions, I want to say it's not common to pop access-type via streams, but maybe I'm just unadventurous.