Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!caen!uflorida!travis!hcx2.ssd.csd.harris.com!bill
From: bill@hcx2.ssd.csd.harris.com (Bill Leonard)
Newsgroups: comp.lang.fortran
Subject: Re: Characters in List I/O and FORTRAN standard
Message-ID: <3625@travis.csd.harris.com>
Date: 10 Jun 91 14:56:26 GMT
References: <50175@ut-emx.uucp>
Sender: news@travis.csd.harris.com
Reply-To: bill@hcx2.ssd.csd.harris.com (Bill Leonard)
Distribution: na
Organization: Harris Computer Systems Division, Fort Lauderdale, FL
Lines: 28

In article <50175@ut-emx.uucp>, michael@crown.as.utexas.edu (Michael Lemke) writes:
> How should the following program react according to the standard if the input is 'abc'
> (including the quotes)?
> 
> 	READ( 5, * ) I
> 	END
> 
> I'd expect it to bomb so that I can react with IOSTAT or the like. Both
> VAX/VMS and SUN behave like that but on the Cray with CFT77 that seems
> legal. So which machine is violating the standard?

Neither.  X3.9-1978 does not define what constitutes an I/O error, so you
cannot (in general) depend on all "illegal" usage resulting in an IOSTAT or
ERR= branch.

This is a "quality of implementation" issue that must be resolved between
yourself and the vendor.

-- 
Bill Leonard
Harris Computer Systems Division
2101 W. Cypress Creek Road
Fort Lauderdale, FL  33309
bill@ssd.csd.harris.com
---------------------------------------------------------------------------
"Chronologically gifted" -- new government term for "old".  Does this make
babies "chronologically deprived"?
---------------------------------------------------------------------------