Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!sharkey!bnlux0!bam
From: bam@bnlux0.bnl.gov (Bruce A. Martin)
Newsgroups: comp.lang.fortran
Subject: Re: Dates for the different versions of FORTRAN?
Message-ID: <2074@bnlux0.bnl.gov>
Date: 20 Aug 90 19:18:37 GMT
Organization: Grumman SXLS @ Brookhaven National Lab, Upton, NY
Lines: 17

In article <1990Aug17.123818.8951@tukki.jyu.fi> sakkinen@jytko.jyu.fi (Markku Sakkinen) writes:
>...
>In article <140686@sun.Eng.Sun.COM> wsb@boise.Eng.Sun.COM (Walt Brainerd) writes:
>>In article <9008151155.AA11309@thep.lu.se>, magnus@THEP.LU.SE (Magnus Olsson) writes:
>...
>There is at least one true incompatibility in DO loops.
>STANDARD Fortran 66 allowed jumps into DO loops from the outside
>under the rather complicated "extended range" rules.
>STANDARD Fortran 77 prohibits such jumps completely.

Quite true.

X3J3 actually promised (in public comment responses) that this capability
would be restored -- in a cleaner way -- in the next revision.  In fact,
a safe "extended range" capability is one of the functionalities (i.e
functional requirements) which the INTERNAL subroutine feature was designed
to satisfy.  (MODULE capabilities also satisfy this need, to some extent.)