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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1fbce91fa69716f7 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: What good are File_Access's? Date: 1998/07/18 Message-ID: #1/1 X-Deja-AN: 372697316 References: <6oo80p$m20$1@nnrp1.dejanews.com> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 900786561 27780 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-07-18T00:00:00+00:00 List-Id: T.E.D. said >It looks to me like the whole point of the File_Access type in Ada.Text_IO is >to allow Standard_Output and Current_Output (and the same functions for Input >and Error) to be compared in order to see if I/O has been redirected somehow. >However, when I compile and execute a DOS program using ObjectAda on NT, >Ada.Text_IO.Current_Output and Ada.Text_IO.Standard_Output are *not* equal. If >I do an Ada.Text_IO to either, it gets printed in my shell window. > >So if I can't use the equality operations of File_Access to see where output >is going, what was the type put in there for? There's nothing else other than >the Standard* and Current* functions that give me one, and the only >operations allowed are equality comparison and assignment. No, the point of this feature is to allow you to save and restore the value of Current_Output. Ted's theory is interesting, but there is nothing in the RM to suggest that this equality test is expected to work, let alone required to work! Indeed it is easy to imagine that two values designating the same file would very likely not be equal.