Groups | Search | Server Info | Login | Register
Groups > sci.electronics.design > #739980
| From | John Levine <johnl@taugh.com> |
|---|---|
| Newsgroups | sci.electronics.design, comp.arch.embedded |
| Subject | Re: Sorry re history of Fortran, good post on LinkedIn |
| Date | 2026-02-01 02:43 +0000 |
| Organization | Taughannock Networks |
| Message-ID | <10lmel8$2co0$1@gal.iecc.com> (permalink) |
| References | <a466fba3-4f96-5968-faef-db94f1e721a5@insomnia247.nl> <10llkdf$apev$1@paganini.bofh.team> <10lm24t$iqv$1@gal.iecc.com> <10lm30h$bs2e$1@paganini.bofh.team> |
Cross-posted to 2 groups.
According to Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com>: >Dear oh dear. Sorry. Whatever comp.compilers post I am thinking of, I >read it a long time ago and I do not remember it intimately, and it is >about versions of FORTRAN from before I became born, or . . . I am >imagining it. Fortran 66 was the first Fortran standard and it largely codified what the existing IBM FORTRAN compilers did so, nope. >What happened to the comp.compilers mbox archives? Happy New Year! >(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!) They're still on my server but since nobody had looked at them for years, I turned off FTP. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-29 14:26 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 09:04 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-29 17:57 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 10:59 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 00:48 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 17:01 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 01:28 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 15:14 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 11:52 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:05 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 12:34 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:29 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 20:59 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 03:06 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-02 00:17 +1100
Re: Excel and accountants, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-01-31 23:21 +0000
Re: Excel and accountants, good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 16:22 -0800
Re: Excel and accountants, good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-02-01 02:13 +0000
Re: Excel and accountants, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 19:31 -0700
Re: Excel and accountants, good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 21:58 +0100
Re: Excel and accountants, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-02-01 14:36 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 03:56 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 15:23 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 14:36 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:31 +1100
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 14:59 +1100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 10:15 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 00:06 +1100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 13:43 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 02:18 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 08:04 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 03:51 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 09:46 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 20:00 +0000
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-30 22:49 +0100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 22:52 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:02 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 13:33 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 01:31 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 19:16 +0000
Re: history of Fortran, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-01-31 23:10 +0000
Sorry re history of Fortran, good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 23:25 +0000
Re: Sorry re history of Fortran, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-02-01 02:43 +0000
Re: Sorry re history of Fortran, good post on LinkedIn OrangeFish <OrangeFish@invalid.invalid> - 2026-02-01 18:00 -0500
Re: history of Fortran, good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 22:11 +0100
Re: history of Fortran, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-02-01 14:42 -0700
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:36 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 15:53 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:14 +1100
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-31 11:21 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:34 -0800
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-31 21:42 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 13:36 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:57 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 03:10 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-02 00:37 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 07:36 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-03 16:27 +1100
Re: good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 22:21 +0100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-31 09:00 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 15:45 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 14:26 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 13:53 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:25 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:41 -0800
Re: good post on LinkedIn Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-31 17:33 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 10:07 -0800
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 11:26 -0700
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 22:04 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 07:38 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-03 16:37 +1100
Re: good post on LinkedIn Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-30 15:06 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 11:55 -0800
Re: good post on LinkedIn wmartin <wwm@wwmartin.net> - 2026-01-30 11:27 -0800
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 18:54 -0800
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 23:26 -0700
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-31 09:22 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 02:50 -0700
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 04:36 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 09:24 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 09:56 -0700
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 10:05 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 14:22 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 19:09 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 22:16 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 22:27 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 03:40 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 22:46 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 15:20 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 08:44 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 17:13 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:55 -0800
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 08:15 -0800
csiph-web