SEQUENTIA_IO and stdin/stdout

SEQUENTIA_IO and stdin/stdout

[Lo Shu]

Hi community,

I came from C world and brought the question: how I can open stdin or
stdout as a SEQUENTIAL file?

Thank you.

Re: SEQUENTIA_IO and stdin/stdout (Standard_Input, Standard_Output)

[Larry Kilgallen]

In article <55cccaab.0310140444.4ac20d7f@posting.google.com>, iin@rgdata.ukrtel.net (Lo Shu) writes:

> I came from C world and brought the question: how I can open stdin or
> stdout as a SEQUENTIAL file?

Parameterless function Text_IO.Standard_Input returns a value of File_Type.

Function Text_IO.Name takes a value of File_Type as a parameter and returns
the name of the corresponding file.

Re: SEQUENTIA_IO and stdin/stdout (Standard_Input, Standard_Output)

[Marius Amado Alves]

On Tue, 2003-10-14 at 14:29, Larry Kilgallen wrote:
> > I came from C world and brought the question: how I can open stdin or
> > stdout as a SEQUENTIAL file?
> 
> Parameterless function Text_IO.Standard_Input returns a value of File_Type.
> 
> Function Text_IO.Name takes a value of File_Type as a parameter and returns
> the name of the corresponding file.

Are you suggesting the trick of finding out the name of Standard_Output
(say) and then open a sequential file with that name? Sounds clever, but
unfortunately it doesn't work. See my previous reply (actually a
forward) for a 'proper' solution to this problem.

Re: SEQUENTIA_IO and stdin/stdout (Standard_Input, Standard_Output)

[Robert I. Eachus]

Marius Amado Alves wrote:

> Are you suggesting the trick of finding out the name of Standard_Output
> (say) and then open a sequential file with that name? Sounds clever, but
> unfortunately it doesn't work. See my previous reply (actually a
> forward) for a 'proper' solution to this problem.

Technically, it may or may not work.  For example, Standard_Output could 
be assigned to a file on the command line when running the program. Then 
  Standard_Output could be closed, and the file reopened by name in 
Sequential_IO.  But agreed, using Streams is the way to go.

-- 
                                                     Robert I. Eachus

"Quality is the Buddha. Quality is scientific reality. Quality is the 
goal of Art. It remains to work these concepts into a practical, 
down-to-earth context, and for this there is nothing more practical or 
down-to-earth than what I have been talking about all along...the repair 
of an old motorcycle."  -- from Zen and the Art of Motorcycle 
Maintenance by Robert Pirsig

Re: SEQUENTIA_IO and stdin/stdout (Standard_Input, Standard_Output)

[Marius Amado Alves]

On Tue, 2003-10-14 at 23:11, Larry Kilgallen wrote:
> > Are you suggesting the trick of finding out the name of Standard_Output
> > (say) and then open a sequential file with that name? Sounds clever, but
> > unfortunately it doesn't work.
> 
> Why not ?   What error do you get ?

I think the ARM does not guarantee it.
With GNAT no output is produced.
I suppose another compiler could work as desired.

Re: SEQUENTIA_IO and stdin/stdout (Standard_Input, Standard_Output)

[Larry Kilgallen]

In article <mailman.80.1066149976.25614.comp.lang.ada@ada-france.org>, Marius Amado Alves <amado.alves@netcabo.pt> writes:
> On Tue, 2003-10-14 at 14:29, Larry Kilgallen wrote:
>> > I came from C world and brought the question: how I can open stdin or
>> > stdout as a SEQUENTIAL file?
>> 
>> Parameterless function Text_IO.Standard_Input returns a value of File_Type.
>> 
>> Function Text_IO.Name takes a value of File_Type as a parameter and returns
>> the name of the corresponding file.
> 
> Are you suggesting the trick of finding out the name of Standard_Output
> (say) and then open a sequential file with that name? Sounds clever, but
> unfortunately it doesn't work.

Why not ?   What error do you get ?

Re: SEQUENTIA_IO and stdin/stdout (Standard_Input, Standard_Output)

[Larry Kilgallen]

In article <mailman.85.1066173102.25614.comp.lang.ada@ada-france.org>, Marius Amado Alves <amado.alves@netcabo.pt> writes:
> On Tue, 2003-10-14 at 23:11, Larry Kilgallen wrote:
>> > Are you suggesting the trick of finding out the name of Standard_Output
>> > (say) and then open a sequential file with that name? Sounds clever, but
>> > unfortunately it doesn't work.
>> 
>> Why not ?   What error do you get ?
> 
> I think the ARM does not guarantee it.

Which of the three steps is not guaranteed ?

	Finding the value of File_Type

	Finding the name of the corresponding file

	Opening the file

If it is the last, I would expect a failure to open would signal an exception.

> With GNAT no output is produced.
> I suppose another compiler could work as desired.

Re: SEQUENTIA_IO and stdin/stdout (Standard_Input, Standard_Output)

[Marius Amado Alves]

> Which of the three steps is not guaranteed ?
> 
> 	Finding the value of File_Type
> 	Finding the name of the corresponding file
> 	Opening the file
> 
> If it is the last, I would expect a failure to open would signal an exception.

I would to. But GNAT does not complaint. At least with a sequential file
of characters. It simply does not output. Maybe it's because I'm not
closing Standard_Output prior to opening it as a sequential file. But I
wouldn't know how to do that. Procedure Close requires a variable, and
you cannot set a file type variable to Standard_Output (because
File_Type is limited).

I agree some kind of clarification on this issue is desirable. Maybe it
has been done already. Or a binding interpretation. Someone should check
it out ;-) Note Robert Eachus already said "it may or may not work".
Maybe he's willing to elaborate ;-)

Personally I don't feel comfortable with two things:

1. The (external) name of a standard channel. Even in C this does not
exist. GNAT says "*stdout", "*stdin". Note the asterisk. This reeks of implementation dependency. I
seem to remember MS-DOS having "CON" for this. I think the ARM is silent
on this anyway.

2. Crossing information between Text_IO and (an instance of)
Sequential_IO. Even if this information is just the name of the external
file.

In sum: there is doubtful solution (and erroneous with GNAT, or so it
seems), and there is an alternate, legal solution. The choice should be
clear.

As I indicated before, I suspect Ada has a weak point here. Namely
binding the standard channels exclusively to Text_IO. Surely the
standard channel concept is less dependent of file format than that.

Re: SEQUENTIA_IO and stdin/stdout (Standard_Input, Standard_Output)

[Frank J. Lhota]

"Marius Amado Alves" <amado.alves@netcabo.pt> wrote in message
news:mailman.95.1066291541.25614.comp.lang.ada@ada-france.org...
> As I indicated before, I suspect Ada has a weak point here. Namely
> binding the standard channels exclusively to Text_IO. Surely the
> standard channel concept is less dependent of file format than that.

I know of no language that has a portable method for accessing the standard
channels (standard input, standard output, and standard error) in any
fashion other than as a text file.