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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c64c5909c07a2300 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-01-09 08:12:14 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!newsfeed00.sul.t-online.de!t-online.de!news.dtag.de!RRZ.Uni-Koeln.DE!uni-duisburg.de!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.ada Subject: Re: Ada way to read/write to character file Date: Wed, 9 Jan 2002 16:12:13 +0000 (UTC) Organization: GMUGHDU Message-ID: References: NNTP-Posting-Host: l1-hrz.uni-duisburg.de X-Trace: a1-hrz.uni-duisburg.de 1010592733 940 134.91.4.34 (9 Jan 2002 16:12:13 GMT) X-Complaints-To: usenet@news.uni-duisburg.de NNTP-Posting-Date: Wed, 9 Jan 2002 16:12:13 +0000 (UTC) User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (HP-UX/B.11.00 (9000/800)) Xref: archiver1.google.com comp.lang.ada:18691 Date: 2002-01-09T16:12:13+00:00 List-Id: Michael Bode wrote: : tmoran@acm.org writes: :> Given timing, error conditions, dropped lines, and the likelihood of :> non-text data, I wonder how often you would actually want to do :> "sequential text I/O" on an RS232 port. : : ... : for a linear axis, 2 CCTV cameras and a scope. So I guess I will have to : do that quite often :-). The point is, I think, that Text_I/O is for text, where text refers to the Ada notion of text, which includes lines, columns, pages and what not; all of these give special meaning to some Character values that you might not want to be that special for your devices. So, when 0S services are called for, call the OS. Some package producers have sets of subprograms to make things easier. If you dig the archives for RS232/COM and Ada... Moreover, if you want to live on the paranoia side, you might want to consider it an assumption to consider OS's character handling to be 8 bits chunk handling in sequential no-endian order. And might it not be adventurous in some circumstances, like a multi-access situation, to think that you would have to put hardware in a required state just once at the start of a program? Georg