Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sdcrdcf.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!pmontgom
From: pmontgom@sdcrdcf.UUCP (Peter Montgomery)
Newsgroups: net.micro.pc,net.lang.f77
Subject: Re: stupid problem in fortran
Message-ID: <1930@sdcrdcf.UUCP>
Date: Fri, 26-Apr-85 18:54:30 EDT
Article-I.D.: sdcrdcf.1930
Posted: Fri Apr 26 18:54:30 1985
Date-Received: Tue, 30-Apr-85 08:04:49 EDT
References: <370@sdchema.UUCP> <614@utcs.UUCP>
Reply-To: pmontgom@sdcrdcf.UUCP (Peter Montgomery)
Organization: System Development Corp. R+D, Santa Monica
Lines: 25
Xref: watmath net.micro.pc:3812 net.lang.f77:271
Summary: 

In article <614@utcs.UUCP> tj@utcs.UUCP (tj) writes:
>
>well, I thought I knew... but I didn't... I recently had an experience with IBM
>mainframe fortran where I coded  cout = 'x' // cout and instead of getting
>an x concatinated in front I got the first character replaced with the x.
>IBM documents this as a restriction, I call it and yours a bug!!!
>tjones

Section 10.4 of the FORTRAN standard, ANSI X3.9-1978, p. 10-2 defines the
form of a character assignment statement to be

		v = e

where v is a variable, array element, or substring, and e is a character
expression.  It also states that "None of the character positions being
defined in v may be referenced in e".  So this is indeed a restriction.
If you don't obey the rules, you can't expect your program to work.

-- 
			Peter Montgomery

	{aero,allegra,bmcg,burdvax,hplabs,
	 ihnp4,psivax,randvax,sdcsvax,trwrb}!sdcrdcf!pmontgom

Don't blame me for the crowded freeways - I don't drive.