Re: The concept of a record



Klaus Wacker wrote:
(snip)

In formatted I/O, yes. In un formatted I/O the concept of a line
doesn't exist.

I would probably say that even in FORMATTED I/O the concept of
line doesn't exist. The standard, even Fortran 2003, defines
I/O in terms of records (or logical records).

The one place it does mention lines is for Fortran source, which
is defined as lines, continuation lines, etc.

A Fortran record sent to a printer would normally be one print line,
and if sent to a card punch one card. On disk or tape it is just
a logical record. (The exception, it seems, is if a program is
outputting Fortran source statements.)

-- glen

.



Relevant Pages

  • Re: Disney reservations system
    ... memories of FORTRAN IV and using a card punch. ... was a huge Burroughs mainframe that took up most of the school's ... basement. ...
    (rec.arts.disney.parks)
  • Re: printing in fortran
    ... Printf has a variable ... be aware of the fine print relating to I/O and C interop. ... If you open a file in Fortran, ...
    (comp.lang.fortran)
  • Re: a mergesort
    ... That would depend on how many records are processed, the quality of the I/O runtime, ... True for all lanuages but Fortran ... whereas comparison-based sorting takes time proportional to N.log N. ... 272343 calls to MergeLCP, 46442 skipped merges, 1320049 string comparisons ...
    (comp.lang.fortran)
  • Re: a mergesort
    ... That would depend on how many records are processed, the quality of the I/O runtime, ... True for all lanuages but Fortran ... whereas comparison-based sorting takes time proportional to N.log N. ... 272343 calls to MergeLCP, 46442 skipped merges, 1320049 string comparisons ...
    (comp.lang.fortran)
  • Re: a modest proposal
    ... OS/360 object programs are 80 byte fixed ... I/O using A format. ... file with JCL and associate it with a Fortran I/O unit number? ...
    (comp.lang.fortran)