Path: ...!weretis.net!feeder8.news.weretis.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: R Daneel Olivaw <Danny@hyperspace.vogon.gov>
Newsgroups: comp.lang.fortran
Subject: Re: Is there a way in Fortran to designate an integer value as
 integer*8 ?
Date: Tue, 15 Oct 2024 08:37:07 +0200
Organization: To protect and to server
Message-ID: <vel2ij$nf8b$1@paganini.bofh.team>
References: <vdict2$339ak$1@dont-email.me> <vdir24$35104$1@dont-email.me>
 <vdk718$3bulb$1@dont-email.me> <vdl6fi$3jra3$2@dont-email.me>
 <vdlfpl$3l0f5$1@dont-email.me> <vdmbml$3p2dv$1@dont-email.me>
 <vdmrgc$3rih7$2@dont-email.me> <vegdr2$m3av$1@dont-email.me>
 <vek2ui$1bip4$5@dont-email.me> <vel22c$1jj5p$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 15 Oct 2024 06:37:07 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="769291"; posting-host="XBJBjenliTep7OIZ0g9xdw.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 SeaMonkey/2.53.18.2
X-Notice: Filtered by postfilter v. 0.9.3
Bytes: 2342
Lines: 27

Thomas Koenig wrote:
> Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
> 
>> "DYNOSOR: a set of subroutines for dynamic memory organization in
>> Fortran programs"
>>      https://dl.acm.org/doi/10.1145/954654.954661
>>
>> One of our guys went to an ACM conference in 1977 and came back with
>> this paper.  It was the answer to our memory problems on the Univac
>> 1108, the CDC 7600, and later the IBM 370.
> 
> Only the first page is readable, the rest is behind paywall,
> unfortunately.
> 
>>
>> I converted the memory allocation scheme from a common block in 1992 ???
>> to using the C malloc, realloc, and free library functions.  Worked like
>> a champ on Unix, Vax VMS, IBM mainframes, and PC DOS using various F77
>> compilers.
> 
> If you're already using dynamic allocation, then you can of course
> keep on doing what you are doing.  It will not be officially
> supported, but the likelyhood of this continuing to work is high
> (no guarantees, though).
> 

If it ain't broke, don't fix it.
(unless there are really good reasons)