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,start
X-Google-Attributes: gid103376,public
From: dennison@telepath.com
Subject: What good are File_Access's?
Date: 1998/07/17
Message-ID: <6oo80p$m20$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 372367412
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Fri Jul 17 19:17:46 1998 GMT
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.0; Windows NT; Gateway2000)
Date: 1998-07-17T00:00:00+00:00
List-Id: <comp.lang.ada>

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.

T.E.D.

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum