From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED.2uCIJahv+a4XEBqttj5Vkw.user.gioia.aioe.org!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: General circular buffer example not tied to any specific type Date: Mon, 6 Jul 2020 13:07:06 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <6ca9747e-698f-4d60-8e23-b883da5d9f38o@googlegroups.com> NNTP-Posting-Host: 2uCIJahv+a4XEBqttj5Vkw.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 X-Notice: Filtered by postfilter v. 0.9.2 Content-Language: en-US Xref: reader01.eternal-september.org comp.lang.ada:59364 List-Id: On 06/07/2020 12:34, Simon Wright wrote: > "Jeffrey R. Carter" writes: > >> On 7/6/20 10:11 AM, Simon Wright wrote: >>> >>> Any *definite* type. I don't remember whether that would suit the >>> original requirement in this thread. >> >> I don't think "requirement" applies. "Circular buffer of untyped >> values" is at best a design decision. Trying to bypass the type system >> is usually an indication of a design problem, in my experience. > > Yes. There would have to be some mechanism for the receiving end to > decide what to do with the next lot of bytes! Sure. An example would be implementation of interprocess RPC. The parameters of a RPC would be passed via some pipe implemented as a ring buffer with stream interface on top of it. Since RPC parameters could be of almost any type, here you go. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de