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.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,56525db28240414a
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII
Received: by 10.224.180.205 with SMTP id bv13mr11587855qab.8.1343789806981;
        Tue, 31 Jul 2012 19:56:46 -0700 (PDT)
Received: by 10.68.218.228 with SMTP id pj4mr914099pbc.2.1343789445390;
        Tue, 31 Jul 2012 19:50:45 -0700 (PDT)
Path: 
 a15ni14729222qag.0!nntp.google.com!h9no2041640pbv.0!news-out.google.com!g9ni7594064pbo.0!nntp.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nrc-news.nrc.ca!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: Efficient Sequential Access to Arrays
Date: Fri, 27 Jul 2012 21:38:09 +0200
Organization: cbb software GmbH
Message-ID: <1r34wzj84t5pk$.16y7b4z9l1tan$.dlg@40tude.net>
References: <01983f1c-f842-4b1f-a180-bcef531dad4c@googlegroups.com>
 <87ipdf4vh6.fsf@mid.deneb.enyo.de> <a72rt6Fq5sU1@mid.individual.net>
 <4ce44d2d-d789-42a0-a6ed-035f7f8d58be@googlegroups.com>
 <a79kcjFufvU1@mid.individual.net>
 <f2f61da1-3139-4dfc-b851-8398f27d558d@googlegroups.com>
 <juq271$c11$1@munin.nbi.dk>
 <b18e5dd8-cd07-49df-8011-22e911dc1da0@googlegroups.com>
 <jur52v$ec7$1@dont-email.me>
 <bbb593dd-253b-4a34-9123-cd2cec09f285@googlegroups.com>
 <1d20andzhb0rk.ytxhpkza8tky$.dlg@40tude.net>
 <ea66e6a9-4537-4b17-b7b1-b7b2efc06bf2@googlegroups.com>
 <1qlao21lvhn4q.p95zkkqzzcqz$.dlg@40tude.net>
 <802f6aec-a448-4a41-8320-fbdb5ffa7883@googlegroups.com>
 <1lqose2aygd4r$.ots4i45o7jnz.dlg@40tude.net> <op.wh3e4gzdka8ora@aspire.local>
 <yuf9ihjnld8m$.5lrpenh95rnq.dlg@40tude.net> <op.wh36cxgqka8ora@aspire.local>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: 9A8bJrx4NhDLcSmbrb6AdA.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
X-Received-Bytes: 2969
Content-Type: text/plain; charset="iso-8859-5"
Content-Transfer-Encoding: 8bit
Date: 2012-07-27T21:38:09+02:00
List-Id: <comp.lang.ada>

On Fri, 27 Jul 2012 20:49:35 +0400, Vasiliy Molostov wrote:

> Dmitry A. Kazakov <mailbox@dmitry-kazakov.de> �����(�) � ����� ������ Fri,  
> 27 Jul 2012 12:48:01 +0400:
> 
>> On Fri, 27 Jul 2012 11:01:17 +0400, Vasiliy Molostov wrote:
>> Don't use 'Read/'Input unless overridden, except for some very rare cases
>> when stream is used inside single program. The only 'Read allowed is on the
>> units for which the underlying hardware is guaranteed to handle the
>> representation. Usually it is octet. Anything on top must be overridden.
> 
> I wonder: have you seen a point-out to the fact that units for read/write  
> can be not only characters (as you told), and also that you-self refer to  
> octets (that are not characters), and other units?

In earlier times I saw some piece of serial hardware which was truly
bit-oriented. I don't remember what it was. It is long time dead and
buried. Otherwise only characters and octets. Larger units are never used.
Not in automotive, smart metering, safety where I am working.

A frame grabber could possible represent somewhat different case, but I
doubt anybody would use a stream interface on it.

> What does that mean at all - "Don't use"?

An advice, which you are free to ignore if you know better.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de