Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!mangoe
From: mangoe@umcp-cs.UUCP (Charley Wingate)
Newsgroups: net.lang
Subject: Re: does Fortran 77 allow recursion?
Message-ID: <1397@umcp-cs.UUCP>
Date: Mon, 26-Aug-85 23:45:42 EDT
Article-I.D.: umcp-cs.1397
Posted: Mon Aug 26 23:45:42 1985
Date-Received: Thu, 29-Aug-85 08:26:38 EDT
References: <6600@boring.UUCP>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 17

In article <6600@boring.UUCP> ken@mcvax.UUCP (Amoeba #117) writes:

>>Static allocation is also enforced by the common use of data statements to
>>initialize variables which are then changed during calls to the subroutine.
>>Every Fortran compiler I've ever seen allocates storage so that the
>>changed values persist

>Note that nowhere in the Fortran standard is such persistence
>sanctioned unless the storage resides in COMMON, which must also be
>present in some outine in the current calling chain. Think about
>overlays (ick!) and you will see why this restriction exists.

This is certainly true, but it looks to me as if this sort of storage
management is going to persist.  There are too many programs which rely on
that sort of implementation.

Charley Wingate