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,6543bf63afffd95a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-02-08 08:50:31 PST Path: swrinde!cs.utexas.edu!uwm.edu!news.alpha.net!news.mathworks.com!zombie.ncsc.mil!news.duke.edu!agate!boulder!news.coop.net!news.den.mmc.com!iplmail.orl.mmc.com!usenet From: "Theodore E. Dennison" Newsgroups: comp.lang.ada Subject: Re: Unbuffered Keyboard I/O Date: 8 Feb 1995 15:38:50 GMT Organization: IPL InterNetNews site Message-ID: <3haoia$3aj@theopolis.orl.mmc.com> References: <1995Feb3.071931.1@clstcs> NNTP-Posting-Host: milkyway.orl.mmc.com Date: 1995-02-08T15:38:50+00:00 List-Id: amlombardi@vms4.sci.csupomona.edu wrote: > > I posted earlier about unbuffered keyboard io, well it works really well (i > used the one at owens.ridgecrest.ca.us) but when the package initializes itself > it must screw with the i/o channels some how because the PUT statement does not > work but all the others like PUT_LINE and NE~W_LINE work... PUT actually will > show up after a PUT_LINE or a NE~W_LINE or quitting the program... anyone have > any ideas on how to fix this? Thanx in advance Actually, this is quite common behavior for PUT. On many systems, PUT I/Os are buffered, and only PUT_LINEs and NEW_LINEs flush that buffer. In many OS's (VMS for one) exitting a program automaticly flushes all I/O buffers. I know VAX Ada exihibts this behavior. There may be other Ada's that do it as well. The solution to this in VMS is to either - Use PUT_LINE or NEW_LINE when the text absolutely HAS to be displayed. - Use the SMG package instead of Text_IO - Use QIOs (YUUUUCK!) - Use the FORM parameter when you open the text file to get Text_IO to not buffer any writes (I hope you are an RMS expert!) If you ARE using VAX Ada, I suggest SMG. T.E.D.