public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Russell Nathan Hyer" <russell.hyer@hyerdesign.com>
To: "fortran" <fortran@gcc.gnu.org>
Subject: Technical feedback re F77 and gfortran manual...
Date: Wed, 01 Aug 2018 15:43:00 -0000	[thread overview]
Message-ID: <E1fktHF-0003Q8-Tj@rmmprod07.runbox> (raw)

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

Hi,

First off thanks for the (in the main) great toolset.

Second, recently, I started going backwards in time to learn and use 77 in my test projects. One of the many aspects involved in this set of mini projects is visualizing the data, so naturally like crashing a computer, the next thing to come was a micro web app. So, I noted with interest your documentation and starting point at:

https://gcc.gnu.org/onlinedocs/gfortran/GETENV.html

Though, as someone who reads, writes and breaks and tests his own software, I found that basing my code around this whilst pragmatically correct (ie: gfortran will accept it with no quibbles) it's not actually fortran 77 code at all. And it's basically F or a subset of F95 for the style it uses. I mean, double quotes plus single quotes. Etc. etc.

Problematically, I had submitted a couple of emails into nber.org (at the point where I hadn't quite realised my error) so my email has been published. Though, I've just sent through a correction, so maybe that'll get published.

In the interim, please find attached to this email a 77 programme that does what you outline in the documentation as quoted above, but in 77 style.

Thanks,

Russell

[-- Attachment #2: chaqry.f --]
[-- Type: application/octet-stream, Size: 186 bytes --]

      program chaqry
      implicit none
      character*5 qry
      call getenv('QUERY_STRING', qry)
      print 1
    1 format('Content-type: text/html'//)
      print*, qry
      end

             reply	other threads:[~2018-08-01 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 15:43 Russell Nathan Hyer [this message]
2018-08-01 18:49 ` Janne Blomqvist
2018-08-01 15:50 Russell Nathan Hyer

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=E1fktHF-0003Q8-Tj@rmmprod07.runbox \
    --to=russell.hyer@hyerdesign.com \
    --cc=fortran@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).