Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!jato!vsnyder
From: vsnyder@jato.jpl.nasa.gov (Van Snyder)
Newsgroups: comp.lang.fortran
Subject: Re: Is this a "feature"?
Message-ID: <1991May29.210451.27260@jato.jpl.nasa.gov>
Date: 29 May 91 21:04:51 GMT
References: <1991May23.160841.402@ac.dal.ca> <24424@lanl.gov> <3590@charon.cwi.nl>
Reply-To: vsnyder@jato.Jpl.Nasa.Gov (Van Snyder)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 25

In article <3590@charon.cwi.nl> dik@cwi.nl (Dik T. Winter) writes:
>In article <24424@lanl.gov> jlg@cochiti.lanl.gov (Jim Giles) writes:
> >                                                               In fact, 
> > I seem to remember that in the 66 standard the definition status of a 
> > local variable across calls was not even mentioned.
>But it is.  In the section about variables that become *undefined* when
>executing a return statement.  (From memory: if a variable is assigned to
>within a routine its value becomes undefined when executing a return
>statement.)
>--
>dik t. winter, cwi, amsterdam, nederland
>dik@cwi.nl
Page 29, lines 19-27 of X3.9-1966 (referring to entities not in common):
"If such an entity is in a subprogram, the completion of exection of a RETURN
statement in that subprogram causes all such entities and their associates at
that time (except for initially defined entities that have not been redefined
or become undefined) to become undefined.  In this respect, it should be noted
that the association between dummy arguments and actual arguments is terminated
at the inception of execution of the RETURN statement."


-- 
vsnyder@jato.Jpl.Nasa.Gov
ames!elroy!jato!vsnyder
vsnyder@jato.uucp