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-Thread: a07f3367d7,c19e8df8a75221d0
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed01.chello.at!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Mon, 31 Aug 2009 12:05:03 +0200
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Q: Line_IO
References: <4a9b045a$0$31875$9b4e6d93@newsspool3.arcor-online.net>
 <7225bda9-8757-4c5c-bb44-b3be21a1e1f9@p36g2000vbn.googlegroups.com>
In-Reply-To: 
 <7225bda9-8757-4c5c-bb44-b3be21a1e1f9@p36g2000vbn.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <4a9ba04a$0$32678$9b4e6d93@newsspool2.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 31 Aug 2009 12:04:58 CEST
NNTP-Posting-Host: b8c7b2dc.newsspool2.arcor-online.net
X-Trace: 
 DXC=?SDY8gn7:k\V0Pe9PRnbJ\A9EHlD;3YcR4Fo<]lROoRQ^YC2XCjHcbY0DWemF[Lil\;9OJDO8_SKVNSZ1n^B98iZ<7@?6j9S6RR
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:8071
Date: 2009-08-31T12:04:58+02:00
List-Id: <comp.lang.ada>

Martin schrieb:

> Nice one...I'll try these out on Win23 and see what happens :-)

Thanks.  As is, the program will raise NAME_ERROR on Win32: It
still seems impossible to name the standard streams for
Stream_IO.Open on Win32?  The package has worked with (other) named
files, though.

> But surely "Put_Line" and "Get_Line" are preferable subprogram
> names?...

The names Put_Line (for Print) and Get_Line (for Getline)
could suggest that these are perfect replacements.
For Print, that is basically the case for standard output,
I think.
Getline, however, needs a little more care than Get_Line
when using it.  At the moment, at least.