Scribd
Upload
28 views

Introduction To Programming With Fortran 90: Advanced I/O and Files

Advanced I / O features some are useful But ONLY in Fortran 2003 some are esoteric or tricky to use. Specify ADVANCE='no' in the read or WRITE This is called non-advancing I / o.

Uploaded by

Elexsandro Rangel
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
28 views

Introduction To Programming With Fortran 90: Advanced I/O and Files

Advanced I / O features some are useful But ONLY in Fortran 2003 some are esoteric or tricky to use. Specify ADVANCE='no' in the read or WRITE This is called non-advancing I / o.

Uploaded by

Elexsandro Rangel
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 27

Introduction to Programming with Fortran 90

Advanced I/O and Files


Nick Maclaren Computing Service

[email protected], ext. 34761 November 2007

Introduction to Programming with Fortran 90 p. 1/?

Summary
This will describe some advanced I/O features Some are useful but only in Fortran 2003 Some are esoteric or tricky to use

The points here are quite important


Excluded only on the grounds of time There is a lot more in this area Please ask if you need any help

Introduction to Programming with Fortran 90 p. 2/?

Partial Records in Sequential I/O


Reading only part of a record is supported Any unread data in the record are skipped The next READ uses the next record Fortran 90 allows you to change that But ONLY for formatted, external I/O Specify ADVANCE=no in the READ or WRITE This is called non-advancing I/O

Introduction to Programming with Fortran 90 p. 3/?

Non-Advancing Output
You can build up a record in sections
WRITE (*, (a), ADVANCE=no) value = IF (value < 0.0) THEN WRITE (*, ("None")) value ELSE WRITE (*, (F5.2)) value ENDIF

This is, regrettably, the only portable use

Introduction to Programming with Fortran 90 p. 4/?

Use for Prompting


WRITE (*, (a), ADVANCE=no) Type a number: READ (*, *) value

That will usually work, but may not The text may not be written out immediately Even using FLUSH may not force that Too many prompts may exceed the record length

Introduction to Programming with Fortran 90 p. 5/?

Non-Advancing Input
You can decode a record in sections Just like for output, if you know the format Reading unknown length records is possible Here are two recipes that are safe and reliable Unfortunately, Fortran 90 and Fortran 2003 differ

Introduction to Programming with Fortran 90 p. 6/?

Recipe (1) - Fortran 90


CHARACTER, DIMENSION(4096) :: buffer INTEGER :: count READ (1, (4096a), ADVANCE=no, SIZE=count, & EOR=10, EOF=20) buffer

The EOR branch is taken if the record is short The following happens whether or not it is SIZE returns the number of characters read

Introduction to Programming with Fortran 90 p. 7/?

Recipe (2) - Fortran 2003


USE ISO_FORTRAN_ENV CHARACTER, DIMENSION(4096) :: buffer INTEGER :: status, count READ (1, (4096a), ADVANCE=no, SIZE=count, & IOSTAT=status) buffer

If IOSTAT is IOSTAT_EOR, the record is short If IOSTAT is IOSTAT_EOF, we are at end-of-le SIZE returns the number of characters read The Fortran 90 recipe works, but this is cleaner

Introduction to Programming with Fortran 90 p. 8/?

General Free-Format Input


Can read in whole lines, as described above
And then decode using CHARACTER operations You can also use internal les for conversion

Can use some other language for conversion


I use Python, but Perl is ne, too Use it to convert to a Fortran-friendly format

You can call C to do the conversion


That isnt always as easy as people think it is

Introduction to Programming with Fortran 90 p. 9/?

List-Directed I/O (1)


This course has massively over-simplied All you need to know for simple test programs It is used mainly for diagnostics etc. Here are a few of its extra features Separation is by comma, spaces or both That is why comma needs to be quoted Theoretically, that can happen on output, too

Introduction to Programming with Fortran 90 p. 10/?

List-Directed I/O (2)


You may use repeat counts on values 100*1.23 is a hundred repetitions of 1.23 That is why asterisk needs to be quoted Theoretically, that can happen on output, too There may be null values in input 1.23 , , 4.56 is 1.23 , null value, 1.234.56 100* is a hundred null values Null values suppress update of the variable

Introduction to Programming with Fortran 90 p. 11/?

List-Directed I/O (3)


As described, slashes (/) terminates the call That is why slash needs to be quoted Before using it in complicated, important code:

Read the specication, to avoid gotchas Work out exactly what you want to do with it

Introduction to Programming with Fortran 90 p. 12/?

Formatted Input for REALs


m in Fn.m etc. is an implied decimal point It is used only if you dont provide one The k in En.mEk is completely ignored And there are more historical oddities Here is an extended set of rules

Use a precision of zero (e.g. F8.0) Always include a decimal point in the number Dont use the P or BZ descriptors for input Dont set BLANK=zero in OPEN or READ

Introduction to Programming with Fortran 90 p. 13/?

The Sordid Details


If you want to know, read the actual standard You wont believe me if I tell you! And dont trust any books on this matter They all over-simplify it like crazy In any case, I doubt that any of you care Follow the above rules and you dont need to

Introduction to Programming with Fortran 90 p. 14/?

Choice of Unit Number


Preconnected units are open at program start Includes at least ones referred to by UNIT=*

OPEN on them will close the old connection


Can check for an open unit using INQUIRE Fortran 2003 has a way of getting their numbers Has names in the ISO_FORTRAN_ENV module Critical only for signicant, portable programs

Introduction to Programming with Fortran 90 p. 15/?

INQUIRE By File (1)


Inquire by le checks if a le exists
LOGICAL :: here INQUIRE (FILE=name, EXIST=here)

Existence may not mean what you expect E.g. a new, output le may be open but not exist

Introduction to Programming with Fortran 90 p. 16/?

INQUIRE By File (2)


Other queries almost always return unknown Many features make no sense under POSIX But others are just implementation deciencies However, at least they DO say unknown And dont simply return plausible nonsense READ=, READWRITE= and WRITE= give the access permissions But no current compiler supports them . . .

Introduction to Programming with Fortran 90 p. 17/?

INQUIRE By Unit (1)


Inquire by unit primarily does two things: Checks if the unit is currently connected Returns the record length of an open le
LOGICAL :: connected INQUIRE (UNIT=number, OPENED=connected) INTEGER :: length INQUIRE (UNIT=number, RECL=length)

You can ask about both together, of course

Introduction to Programming with Fortran 90 p. 18/?

INQUIRE By Unit (2)


There are other potentially useful speciers It is worth checking them under new versions You can get all of the speciers used for OPEN Could be useful when writing generic libraries They typically work only using inquire by unit SIZE gives the size of the le, probably in bytes This is only in Fortran 2003 See the references for details on them

Introduction to Programming with Fortran 90 p. 19/?

Unformatted I/O
Using pipes or sockets is tricky So is unformatted I/O of derived types

Ask for advice if you need to do these

Introduction to Programming with Fortran 90 p. 20/?

Namelist
Namelist is a historical oddity, new in Fortran 90 This sounds impossible, but I assure you is true

Not recommended, but not deprecated, either

Introduction to Programming with Fortran 90 p. 21/?

STREAM Files
Fortran 2003 has introduced STREAM les These are for interchange with C-like les They provide all portable features of C

I dont know how well they will work in practice


Please tell me if you investigate

Introduction to Programming with Fortran 90 p. 22/?

I/O of Derived Types


The DT descriptor has been mentioned You can do almost anything you need to But this course cannot cover everything

Introduction to Programming with Fortran 90 p. 23/?

Asynchronous I/O
Mainframes proved that it is the right approach Fortran 2003 introduced it

For complicated reasons, you should avoid it This has nothing to do with Fortran
Dont use POSIX asynchronous I/O, either And probably not Microsofts . . .

Introduction to Programming with Fortran 90 p. 24/?

Oddities of Connection
Try to avoid these, as they are confusing
You will see them in some of the references Files can be connected but not exist Ones newly created by OPEN may be like that Units can be connected when the program starts Ask me if you want to know why and how OPEN can be used on an existing connection It modies the connection properties

Introduction to Programming with Fortran 90 p. 25/?

Other Topics
There are a lot more optional features You must read Fortrans specications for them Fortran 2003 adds many slightly useful features Most compilers dont support many of them yet The above has described the most useful ones And a few features should be avoided entirely For more on this, look at the OldFortran course

Introduction to Programming with Fortran 90 p. 26/?

Last Reminder
Be careful when using Fortran I/O features They dont always do what you expect It is much cleaner than C/POSIX, but . . . Fortrans model is very unlike C/POSIXs Fortrans terminology can be very odd The underlying C/POSIX can show through In addition to Fortrans own oddities

Introduction to Programming with Fortran 90 p. 27/?

You might also like