From: Roland Hughes <roland@logikalsolutions.com>
To: fortran@gcc.gnu.org
Subject: F77 indexed file support
Date: Tue, 7 Mar 2023 16:18:58 -0600 [thread overview]
Message-ID: <8f40b52e-c264-d1e4-06dd-fb9990a64bb8@logikalsolutions.com> (raw)
All,
I'm getting back into Fortran after many years away and was going to
start with my goto kick the tires application. Basically the lottery
tracking system found in this book.
https://www.theminimumyouneedtoknow.com/app_book.html
The first cut was Fortran 77 on the VAX. There we could create/use
indexed files with OPEN statements much like this:
210 OPEN (UNIT=K_DRAW_CHAN,
1 FILE=DRAWING_DATA,
2 STATUS='OLD',
3 ORGANIZATION='INDEXED',
4 ACCESS='KEYED',
5 RECORDTYPE='FIXED',
6 FORM='UNFORMATTED',
7 RECL=K_DRAWING_RECORD_SIZE/4,
8 CARRIAGECONTROL='FORTRAN',
9 KEY=(1:8:CHARACTER),
1 DISP='KEEP',
2 IOSTAT=L_DRAW_ERR,
3 ERR=999)
The ORGANIZATION='INDEXED' is key.
GnuCOBOL
https://gnucobol.sourceforge.io/
uses the BerkleyDB (sp?) library so the standard COBOL indexed file
support from the big computers can at least be mimicked.
I'm searching everywhere and I cannot find Gnu Fortran (any flavor)
having an ORGANIZATION clause in the OPEN(). Is this true? Are we forced
to use some SQLite wrapper library when porting VAX/VMS FORTRAN to Linux?
Btw, is there a "search" utility for the archives or do I have to pull
down all of the zip files, unzip into directory, and grep to look for
stuff like this? I'm guessing it has come up before.
Thanks,
Roland
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
next reply other threads:[~2023-03-07 22:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 22:18 Roland Hughes [this message]
2023-03-07 22:58 ` Thomas Koenig
2023-03-08 5:32 ` Arjen Markus
2023-03-08 13:31 ` Roland Hughes
2023-03-08 7:57 ` Bernhard Reutner-Fischer
2023-03-08 13:32 ` Roland Hughes
2023-03-08 14:30 ` Arjen Markus
2023-03-08 15:19 ` Roland Hughes
2023-03-09 8:09 ` Arjen Markus
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=8f40b52e-c264-d1e4-06dd-fb9990a64bb8@logikalsolutions.com \
--to=roland@logikalsolutions.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).