From: Ron Young <rly1@embarqmail.com>
To: tuhs@tuhs.org
Subject: Re: [TUHS] > there is no way that FORTRAN can be described in any syntax
Date: Sun, 02 Dec 2018 21:31:47 -0800 [thread overview]
Message-ID: <7E.F0.08702.4CFB40C5@smtp04.onyx.dfw.sync.lan> (raw)
In-Reply-To: <201812030336.wB33axfq080387@tahoe.cs.Dartmouth.EDU>
Your message dated: Sun, 02 Dec 2018 22:36:59 -0500
--------
>
> I did just that. The National Bureau of Standards picked it up
> in NBS Handbook 131, "Using ANS FORTRAN" (1980). It is expressed
> in the same formalism that Burroughs used for Algol.
>
> Doug
a couple of more data points:
Arthur Sale wrote an article on classifying fortran statements,
Volume 14 Number 1 of the Computer Journal that describes how to
classify fortran statements into 1 of 36 types.
URL:https://www.researchgate.net/profile/Arthur_Sale/publication/220459829_The_classification_of_FORTRAN_statements/links/02e7e5181a234c6545000000/The-classification-of-FORTRAN-statements.pdf).
by using the above, you can do some preprocessing to correct spacing,
line continuations, remove sequence numbers (cols 73-80) and other
formatting to make parsing easier.
John Levine wrote a ftn77 subset parser using lex and yacc (the shar
file that I have is dated Nov 1988).
-ron
===============================================================================
Ron Young rly1@embarqmail.com
next prev parent reply other threads:[~2018-12-03 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 3:36 Doug McIlroy
2018-12-03 5:31 ` Ron Young [this message]
2018-12-03 20:10 ` Paul Winalski
2018-12-03 20:55 ` Ron Young
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=7E.F0.08702.4CFB40C5@smtp04.onyx.dfw.sync.lan \
--to=rly1@embarqmail.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).