Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.fortran
Subject: Re: Feed control
Date: Thu, 4 Apr 2024 20:33:06 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 22
Message-ID: <uun2q1$s192$2@dont-email.me>
References: <uujitq$3tv68$1@dont-email.me> <uukf8i$4v8t$1@dont-email.me>
	<uuklo7$6hdl$1@dont-email.me> <uukrof$7p2o$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 04 Apr 2024 20:33:06 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="b2ebab76618f2906d24b8f2b6b05668a";
	logging-data="918818"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19dSZfyaQZd+cy0m2LaV4P/"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:Y0S0lsqKsDcBwrFnL8izV/iDjG0=
Bytes: 1929

On Wed, 3 Apr 2024 19:20:30 -0500, Lynn McGuire wrote:

> On 4/3/2024 5:38 PM, Lawrence D'Oliveiro wrote:
>
>> On Wed, 3 Apr 2024 15:47:13 -0500, Lynn McGuire wrote:
>> 
>>> ... we still use Fortran carriage control in column 1 in all of our
>>> main write statements, about 40,000 of them in our code.
>> 
>> Never too soon to start fixing them. Do it one at a time.
> 
> Gotta do them all at once since the carriage control is controlled by
> the OPEN statement.

There is a way to do it: open a second output file, without the Fortran 
carriage control setting. Send both outputs to pipes read by a separate 
filter process that interleaves the lines back into the real output file.

Now you can go through gradually, changing those output statements one by 
one to write to the second file. Once they are all done, you can get rid 
of the first file and the filter process, and resume output directly to 
the output file.