public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arjen Markus <arjen.markus895@gmail.com>
To: Roland Hughes <roland@logikalsolutions.com>
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
	Roland Hughes via Fortran <fortran@gcc.gnu.org>
Subject: Re: F77 indexed file support
Date: Wed, 8 Mar 2023 15:30:48 +0100	[thread overview]
Message-ID: <CAMCbSMqPzW1RKaawyOXF4ZZcNtoNaqAf6_v2FP3C3WUr1r=9jw@mail.gmail.com> (raw)
In-Reply-To: <5b9d7b4a-4932-409e-ee40-b83ef642412d@logikalsolutions.com>

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

Well, that is indeed something completely different.My main frame of
reference (pun not intentional) of that era was our IBM mini, I am not
quite sure of the type number, 3270? It had a very specific record
structure for unformatted files. Normally that was almost completely
hidden, except in the job control, but when we started exchanging data
files with the personal computers that were then coming out, I could write
programs that did the necessary conversions. Jolly good fun. My department
did not use VAXes, other departments did.

So, in your case these files contain data identifiable via some index. Hm,
today you would do that via some library instead of via some builtin
language feature, at least when using Fortran, C, C++, ...

Regards,

Arjen

Op wo 8 mrt 2023 om 14:31 schreef Roland Hughes via Fortran <
fortran@gcc.gnu.org>:

> Thank you!
>
>
> On 3/8/2023 1:57 AM, Bernhard Reutner-Fischer wrote:
> > On 7 March 2023 23:18:58 CET, Roland Hughes via Fortran <
> fortran@gcc.gnu.org> wrote:
> >
> > [ snip namelist IO ]
> >
> >> 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.
> > Indeed we have
> > https://inbox.sourceware.org/fortran/
> >
> > along the traditional pipermail ml interface.
> >
> > thanks,
>
> --
> Roland Hughes, President
> Logikal Solutions
> (630)-205-1593  (cell)
> http://www.theminimumyouneedtoknow.com
> http://www.infiniteexposure.net
> http://www.johnsmith-book.com
>
>

  reply	other threads:[~2023-03-08 14:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 22:18 Roland Hughes
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 [this message]
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='CAMCbSMqPzW1RKaawyOXF4ZZcNtoNaqAf6_v2FP3C3WUr1r=9jw@mail.gmail.com' \
    --to=arjen.markus895@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=rep.dot.nop@gmail.com \
    --cc=roland@logikalsolutions.com \
    /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).