🚀 go-pugleaf

In <1993Jan22.183106.15813@newshost.lanl.gov> jlg@cochiti.lanl.gov (J. Giles) writes:

>In article <1993Jan21.074755.14939@arcetri.astro.it>, lfini@sisifo (Luca Fini) writes:
>|> W. Donald Rolph (a722756@roper.mc.ti.com) wrote:
>|> : 
>|> : Equivalence is in some cases the only possiblity for run time memory allocation
>|> :
>|> 
>|> Equivalence is *not* a run rime memory allocation, you simply call the
>|> same memory area with different names (and possibly use it as different
>|> data types).

>Yes, and that permits you to do run-time management of a statically
>allocated "maximum" space.  You figure out what the maximum memory
>you ever need is and you statically allocate that much:

>      PARAMETER (MAXMEM=1000000)
>      COMMON /MEMORY/ MEM(MAXMEM)

>This reserves one million integer sized words.  Now, you can write
>a MALLOC routine which returns avalable space from within this array
>in the form of an index (you actually have two mallocs, one for
>integers and reals, the other for complex and doubles - since the
>indices must be scaled differently).  To use:

You're not seriously suggesting that this be used in production code,
are you?  If you are, is this intended as job security?
-- 
Howard S Shubs    hshubs@bix.com          For to win 100 victories in 100
The Denim Adept   hshubs@cis.umassd.edu   battles is not the acme of skill.