home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.fortran
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!wupost!emory!swrinde!cs.utexas.edu!hellgate.utah.edu!lanl!cochiti.lanl.gov!jlg
- From: jlg@cochiti.lanl.gov (J. Giles)
- Subject: Re: unformatted output: << SUMMARY >>
- Message-ID: <1992Nov6.210729.23032@newshost.lanl.gov>
- Sender: news@newshost.lanl.gov
- Organization: Los Alamos National Laboratory
- References: <1992Nov3.135015.14373@syma.sussex.ac.uk> <1992Nov4.102804.8781@uts.uni-c.dk> <1992Nov4.160112.26525@chpc.utexas.edu>
- Date: Fri, 6 Nov 1992 21:07:29 GMT
- Lines: 24
-
- In article <1992Nov4.160112.26525@chpc.utexas.edu>, michael@chpc.utexas.edu (Michael Lemke) writes:
- |> [...]
- |> Doesn't have the record *number* to be stored at some place as well?
- |> Nothing stops you from doing
- |>
- |> open( ,.... access='direct', .... )
- |> write( ..., rec=777 ) data
- |> write( ..., rec=32 ) mode_data
- |> close( ... )
- |>
- |> which gives you just two records of data and lots of `holes'. Or am I
- |> missing something?
-
- The standard doesn't actually *say* whether writing a file this way
- is legal or not. That is, if you write a record number which is
- well beyond the present file length, what happens. The standard
- it silent on this question. *MOST* implementations will simply
- extend the file as necessary and leave the intermediate record
- positions unchanged (that is, containing whatever the system
- patterns the disk with when you extend a file - if the system
- does this important operation!).
-
- --
- J. Giles
-