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!cornell!rochester!pt.cs.cmu.edu!sei!dd
From: dd@sei.cmu.edu (Dennis Doubleday)
Newsgroups: comp.lang.ada
Subject: Re: Help! DEC/Ada TEXT_IO & QIO don't get along
Message-ID: <8513@aw.sei.cmu.edu>
Date: 10 Feb 89 13:52:40 GMT
References: <7250@pyr.gatech.EDU>
Organization: Carnegie-Mellon University (Software Engineering Institute), Pgh, PA
In-reply-to: tynor@pyr.gatech.EDU's message of 9 Feb 89 22:46:12 GMT
List-Id: <comp.lang.ada>

(Steve Tynor) writes:

>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.

Text_IO and QIO cooperated nicely in a text editor I worked on that
used Text_IO in line editor mode and QIOs in full-screen editor mode.
I didn't experience this problem.  However, I used the QIO interface
calls supplied by DEC in the package STARLET.  Are you using these?
If not, perhaps your problem is in the QIO package you wrote.

Dennis Doubleday  (dd@sei.cmu.edu)                     _   /|
Software Engineering Institute                         \'o.O'
Carnegie Mellon University                ACK! PTHFT!  =(___)=
Pittsburgh, PA 15213  (412)268-5873                       U