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,ecaf3ca34d49d2e9 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-02-28 10:21:35 PST Path: nntp.gmd.de!stern.fokus.gmd.de!ceres.fokus.gmd.de!zib-berlin.de!fu-berlin.de!zrz.TU-Berlin.DE!netmbx.de!unlisys!news.maz.net!news.ppp.de!xlink.net!howland.reston.ans.net!news.sprintlink.net!uunet!boulder!news.coop.net!news.den.mmc.com!iplmail.orl.mmc.com!usenet From: "Theodore E. Dennison" Newsgroups: comp.lang.ada Subject: Re: Problem with SMG!!!! Date: 28 Feb 1995 18:21:35 GMT Organization: IPL InterNetNews site Message-ID: <3ivpjf$eco@theopolis.orl.mmc.com> References: <1995Feb15.190318.1@clstcs> <3hvj11$pk6@theopolis.orl.mmc.com> NNTP-Posting-Host: payday.orl.mmc.com Date: 1995-02-28T18:21:35+00:00 List-Id: adam@irvine.com (Adam Beneschan) wrote: > "Theodore E. Dennison" writes: > > Unless I'm missing something, when you do screen I/O's with SMG, you > > need to do ALL your screen I/Os with SMG. In other words, you need to > > use the SMG output routines. Forget about Text_IO. > > > Hmmm . . . I've been using SMG$ routines for keyboard input and the > regular SYS$QIOW routines for output, and I've never had a problem. > In other words, there seems to be nothing in VMS that requires that > you use SMG$ for output if you're using it for input. > > VAX Ada may be a different story, however. If TEXT_IO.PUT routines If I remember correctly, TEXT_IO operations are mapped directly to RMS$ routines, not to SYS$QIO routines. I also remember that mixing Text_IO.Put* routines with SMG$ tended to cause problems. SMG$ provides its own text input and output routines, so why not use them? If you "mix-and-match" your I/O routines, you are asking for trouble. To put this in OO terms: Text_IO is an abstraction for user I/O. SMG is a different abstraction for user I/O. Pick one abstraction, and stick with it. T.E.D.