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.8 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!gatech!gitpyr!tynor
From: tynor@pyr.gatech.EDU (Steve Tynor)
Newsgroups: comp.lang.ada
Subject: Help! DEC/Ada TEXT_IO & QIO don't get along
Keywords: Flush QIO TEXT_IO
Message-ID: <7250@pyr.gatech.EDU>
Date: 9 Feb 89 22:46:12 GMT
Organization: Georgia Tech Research Institute
List-Id: <comp.lang.ada>

Help! I need a way to flush the TEXT_IO.STANDARD_OUTPUT file so that I
can switch over to using more primative QIO calls (for screen IO,
cursor motion, etc.) The DEC/Ada Programmer's Runtime Reference Manual
(sec. 2.6.5.2) says that TEXT_IO output is buffered until a NEW_LINE or
NEW_PAGE. However, when I try the following:

     TEXT_IO.PUT_LINE ("this string gets eaten");
     QIO.PUT ("this string gets written where I expect the other");
     -- NOTE: the QIO package is not defined by DEC - I wrote it myself.

things do not behave as documented.  Subsequent calls to TEXT_IO.PUT*
will flush the buffered string, but it's too late... What I need is a
way to explicitly flush STANDARD_OUTPUT. I can't CLOSE and then OPEN
(STANDARD_OUTPUT is a function not a FILE_TYPE, and CLOSE/OPEN treats
the file as in-out). Please don't tell me not to mix TEXT_IO and QIO:
I need unbuffered QIO for fancy screen processing and buffered TEXT_IO
is much faster for other kinds of output.

Any DEC specific ways to flush STANDARD_OUT?

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
No problem is so formidable that you can't just walk away from it.
                     
    Steve Tynor
    Georgia Tech Research Institute
    tynor@gitpyr.gatech.edu