From Newsgroup: comp.lang.fortran

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.
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.lang.fortran

On 4/4/2024 12:09 PM, R Daneel Olivaw wrote:

Gary Scott wrote:

On 4/4/2024 8:52 AM, Dr. What wrote:

Gary Scott wrote to All <=-

  GS> On 4/3/2024 7:43 AM, db wrote:
  > When I learned Fortran many years ago, the first
  > character in a line to be printed (or later,
  > displayed) controlled line or page feed. A blank
  > produced a new line, a "1" a new page. We used these
  > to control what happened.
  >
  > These days, this doesn't seem to be the case, so
  > in a sense, Fortran is no longer backward
  > compatible in this one sense. Or is it?
  >

  GS> This was always, and remains device dependent.

That's not completely true.

Using MS-FORTRAN on my vintage computers, I always have to start my
FORMATs
with "1X".  If I fail to do that, the output, even to the screen, chops >>> off
that first character.

Hmmm.  I'd say that's precisely what "device dependent" means.
Although some behavior in MS Fortran was just bugs.

... Epitaph on a gravestone: Cheerio, see you soon.
___ MultiMail/Linux v0.52

Not at all, the 1X means that the line-feed character is a space.  A "+" there would probably overlay whatever had previously been printed to
that line with something new.
I have used several different compilers on several different
architectures over the years (the newest adhered to the F77 standard)
and the meaning of the first character on a line was common to all of them.

There were very many different devices that had different meanings for
various control characters. There were also devices based on EBCDIC
with completely different character "values" used to achieve a similar
effect. There were also many devices that required multi-character
(/binary) control sequences. Just because there was a frequent
convention on Windows or Linux doesn't mean it was universal.

--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.lang.fortran

On Thu, 4 Apr 2024 20:55:11 -0500, Gary Scott wrote:

Just because there was a frequent
convention on Windows or Linux doesn't mean it was universal.

The conventions predated those platforms by several decades.
--- Synchronet 3.20a-Linux NewsLink 1.114