From: Bob Wilkinson <bob.wilkinson@cristie.com>
To: Joao Martins Correia <Guilherme.Correia@cern.ch>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Program on old fortran IV
Date: Thu, 30 Apr 2020 15:59:42 +0100 [thread overview]
Message-ID: <20200430145942.GB2626659@cristie.com> (raw)
In-Reply-To: <CCFF751B-6479-4CC6-BEC4-C07F4105A632@cern.ch>
On Wed, Apr 29, 2020 at 01:37:25PM +0000, Joao Martins Correia wrote:
> Dear Gcc Helpers
>
> I recovered an old scientific program code written in Fortran IV.
> Still using hollerith assignments - which I think I understand, I can compile it with the many warnings
> regarding essentially 3 things
>
> The program starts running, properly, reads input files and execute some routines, but then gets stuck with strange huge
> numbers that have no apparent reason to be there.
> The problem is in fact that there are no assignment of variable types and there are many commons with different variable names
> that contribute to the confusion when debugging. Setting “implicit none” creates too many errors, since sometimes is not easy
> to assign the type of the variable on a code with 30 routines and more than 5000 lines.
It is many years since I did any FORTRAN programming, but I vaguely
remember that implicit none could be used on a subroutine by
subroutine basis (though that is probably compiler-dependent).
If this works for you, it may make your job easier. I do not like
implicit ...
Bob
--
"We are in the beginning of a mass extinction, and all you can talk
about is money and fairy tales of eternal economic growth."
- Greta Thunberg
next prev parent reply other threads:[~2020-04-30 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 13:37 Joao Martins Correia
2020-04-29 14:24 ` Tim Prince
2020-04-30 14:59 ` Bob Wilkinson [this message]
2020-04-30 16:34 ` Joao Martins Correia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200430145942.GB2626659@cristie.com \
--to=bob.wilkinson@cristie.com \
--cc=Guilherme.Correia@cern.ch \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).