From: KenUnix <ken.unix.guy@gmail.com>
To: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] 3B2/400 Unexpected f77 results
Date: Fri, 24 Mar 2023 18:39:40 -0400 [thread overview]
Message-ID: <CAJXSPs8LjzH5K24Xwcz5H3yt2RO7rFFOXGA6OOq2bqpU2XRWng@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
Hi,
Question. Is anyone aware of a problem with F77 on 3B2/400 running
System V.3 ? When trying to validate a simple program it works as
expected on Linux. See below. But, on Unix V.3 it does not. You do
not get the question until AFTER you enter a number.
Linux:
PROGRAM HELLO
INTEGER AGE
PRINT '(A)', 'Hello, world. Enter your age :'
READ '(A)', AGE
PRINT '(A)', 'You entered :'
print '(A)', AGE
STOP
END
ken@ken-Inspiron-5755:~/fortran$ ./a.out
Hello, world. Enter your age :
73
You entered :
73
Now under Unix
$ ./a.out
73
Hello, world. Enter your age :
You entered :
73
Thanks,
Ken
--
WWL 📚
[-- Attachment #2: Type: text/html, Size: 1237 bytes --]
reply other threads:[~2023-03-24 22:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJXSPs8LjzH5K24Xwcz5H3yt2RO7rFFOXGA6OOq2bqpU2XRWng@mail.gmail.com \
--to=ken.unix.guy@gmail.com \
--cc=tuhs@tuhs.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 NNTP newsgroup(s).