Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.os.vms
Subject: Re: New meets old
Date: Tue, 17 Jun 2025 01:28:29 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 11
Message-ID: <102qgbt$1vtn2$2@dont-email.me>
References: <102pqgr$1q6o0$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 17 Jun 2025 03:28:29 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="d4fee70bccfaaa03c290361a2f8e2731";
	logging-data="2094818"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18M/SKjNtD9k/w8b9aHggSM"
User-Agent: Pan/0.162 (Pokrosvk)
Cancel-Lock: sha1:5XHNlIxwjtnDxmvuQVMho4of+ZQ=

On Mon, 16 Jun 2025 15:15:39 -0400, Arne Vajhøj wrote:

> sys.stdout.writelines(sys.stdin.readlines())
> sys.stdout.writelines(sys.stdin.readlines())

Some interesting semantics going on there. How do you continue reading 
after encountering EOF? How does it reset the EOF condition to let you get 
the second lot of data?

Normally, once an open file gets to EOF, it stays in that state until 
fseek(2) (or equivalent) is called.