Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.folklore.computers > #211682 > unrolled thread
| Started by | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| First post | 2020-06-01 19:25 -0700 |
| Last post | 2020-07-05 16:35 -0700 |
| Articles | 17 on this page of 197 — 32 participants |
Back to article view | Back to alt.folklore.computers
What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-01 19:25 -0700
Re: What ASCII Should Have Been Andy Burns <usenet@andyburns.uk> - 2020-06-02 07:49 +0100
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 00:26 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 00:35 -0700
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-02 08:18 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 02:45 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 02:57 -0700
Re: What ASCII Should Have Been Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-06-02 10:06 +0000
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-02 11:52 +0000
Re: What ASCII Should Have Been songbird <songbird@anthive.com> - 2020-06-02 12:18 -0400
Re: What ASCII Should Have Been Theo <theom+news@chiark.greenend.org.uk> - 2020-06-02 11:31 +0100
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 05:05 -0700
Re: What ASCII Should Have Been daphne@panix.com (Daphne Eftychia Arthur) - 2020-06-03 18:09 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 14:01 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 17:54 -0700
Re: What ASCII actually is John Levine <johnl@taugh.com> - 2020-06-04 02:11 +0000
Re: What ASCII Should Have Been daphne@panix.com (Daphne Eftychia Arthur) - 2020-06-04 03:05 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 20:26 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-04 07:06 -0700
Re: What ASCII Should Have Been daphne@panix.com (Daphne Eftychia Arthur) - 2020-06-04 03:27 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 20:31 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 20:41 -0700
Re: What ASCII Should Have Been Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2020-06-06 02:22 +0800
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-05 11:33 -0700
Re: What ASCII Should Have Been Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2020-06-06 13:58 +0800
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-06 11:10 -0700
Re: What ASCII Should Have Been robin.vowels@gmail.com - 2020-06-02 19:46 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 23:24 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 23:36 -0700
Re: What ASCII Should Have Been Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-06-03 17:22 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 10:33 -0700
Re: What ASCII Should Have Been Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-06-03 20:30 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 13:40 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-04 07:06 -0700
Re: What ASCII Should Have Been Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-06-04 16:59 +0000
Re: What ASCII Should Have Been J. Clarke <jclarke.873638@gmail.com> - 2020-06-03 19:50 -0400
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 17:47 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-04 07:06 -0700
Re: What ASCII Should Have Been Mike Spencer <mds@bogus.nodomain.nowhere> - 2020-06-03 20:53 -0300
Re: What ASCII Should Have Been John Levine <johnl@taugh.com> - 2020-06-04 00:08 +0000
Re: What ASCII Should Have Been Gerard Schildberger <gerard46@rrt.net> - 2020-06-03 17:10 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 17:48 -0700
Re: What ASCII Should Have Been Mike Spencer <mds@bogus.nodomain.nowhere> - 2020-06-04 03:11 -0300
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-04 01:18 -0700
Re: What ASCII Should Have Been Mike Spencer <mds@bogus.nodomain.nowhere> - 2020-06-05 03:50 -0300
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-04 07:06 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-05 00:44 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-05 07:53 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-05 08:04 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-05 10:03 -0700
Re: What ASCII Should Have Been JimP <solosam90@gmail.com> - 2020-06-05 11:05 -0500
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-05 09:27 -0700
Re: What ASCII Should Have Been Dallas <dallas@texas.usa> - 2020-06-05 11:45 -0500
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-05 09:55 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-05 10:16 -0700
Re: What ASCII Should Have Been Ahem A Rivet's Shot <steveo@eircom.net> - 2020-06-05 18:23 +0100
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-05 10:03 -0700
Re: What ASCII Should Have Been Niklas Karlsson <anksil@yahoo.se> - 2020-06-07 15:05 +0000
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-07 09:28 -0700
Re: What ASCII Should Have Been Niklas Karlsson <anksil@yahoo.se> - 2020-06-07 19:56 +0000
Re: What ASCII Should Have Been Dallas <dallas@texas.usa> - 2020-06-07 16:15 -0500
Re: What ASCII Should Have Been Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-06-05 17:31 +0000
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-05 11:24 -0700
Re: What ASCII Should Have Been robin.vowels@gmail.com - 2020-06-05 15:02 -0700
Re: What ASCII Should Have Been Dallas <dallas@texas.usa> - 2020-06-05 17:40 -0500
Re: What ASCII Should Have Been John Levine <johnl@taugh.com> - 2020-06-06 00:10 +0000
Re: What ASCII Should Have Been Dallas <dallas@texas.usa> - 2020-06-05 19:44 -0500
Re: What ASCII Should Have Been John Levine <johnl@taugh.com> - 2020-06-06 01:54 +0000
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-05 10:03 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-05 11:57 -0700
Re: What ASCII Should Have Been JimP <solosam90@gmail.com> - 2020-06-06 11:15 -0500
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-06 11:10 -0700
Re: What ASCII Should Have Been JimP <solosam90@gmail.com> - 2020-06-06 16:14 -0500
Brest U-boat pens (was: Re: What ASCII Should Have Been "Kerr-Mudd,John" <notsaying@invalid.org> - 2020-06-07 10:01 +0000
Re: Brest U-boat pens (was: Re: What ASCII Should Have Been "Kerr-Mudd,John" <notsaying@invalid.org> - 2020-06-07 17:58 +0000
Re: Brest U-boat pens Dallas <dallas@texas.usa> - 2020-06-07 15:54 -0500
Re: What ASCII Should Have Been Joy Beeson <jbeeson@invalid.net.invalid> - 2020-06-06 19:12 -0400
Re: What ASCII Should Have Been J. Clarke <jclarke.873638@gmail.com> - 2020-06-06 19:40 -0400
Re: What ASCII Should Have Been John Levine <johnl@taugh.com> - 2020-06-07 01:22 +0000
Re: What ASCII Should Have Been Dallas <dallas@texas.usa> - 2020-06-06 22:22 -0500
Re: What ASCII Should Have Been Andy Walker <anw@cuboid.co.uk> - 2020-06-07 10:46 +0100
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-07 07:58 -0700
Re: What ASCII Should Have Been Thomas Koenig <tkoenig@netcologne.de> - 2020-06-07 15:37 +0000
Re: What ASCII Should Have Been Gareth Evans <headstone255@yahoo.com> - 2020-06-07 21:52 +0100
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-06 19:44 -0700
Re: What ASCII Should Have Been Alfred Falk <aefalk@telus.net> - 2020-06-07 03:11 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 23:25 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-02 23:27 -0700
Re: What ASCII Should Have Been Andy Walker <anw@cuboid.co.uk> - 2020-06-03 10:40 +0100
Re: What ASCII Should Have Been Andy Walker <anw@cuboid.co.uk> - 2020-06-03 12:05 +0100
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-03 13:08 +0000
Re: What ASCII Should Have Been Andy Walker <anw@cuboid.co.uk> - 2020-06-03 15:47 +0100
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-03 17:20 +0000
Re: What ASCII Should Have Been Thomas Koenig <tkoenig@netcologne.de> - 2020-06-03 17:26 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 10:35 -0700
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-03 18:03 +0000
Re: What ASCII Should Have Been Andy Walker <anw@cuboid.co.uk> - 2020-06-03 19:27 +0100
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-03 18:38 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-03 13:41 -0700
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-03 21:15 +0000
Re: What ASCII Should Have Been Andy Walker <anw@cuboid.co.uk> - 2020-06-04 00:25 +0100
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-04 07:06 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-04 07:06 -0700
Re: What ASCII Should Have Been Thomas Koenig <tkoenig@netcologne.de> - 2020-06-05 18:27 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-05 12:00 -0700
Re: What ASCII Should Have Been Thomas Koenig <tkoenig@netcologne.de> - 2020-06-07 16:52 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-07 10:21 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-07 11:03 -0700
Re: What ASCII Should Have Been Thomas Koenig <tkoenig@netcologne.de> - 2020-06-07 19:08 +0000
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-07 13:00 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-07 16:09 -0700
Re: What ASCII Should Have Been usenet@only.tnx (Questor) - 2020-06-09 09:18 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-09 07:22 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-09 11:51 -0700
Re: What ASCII Should Have Been Rich Alderson <news@alderson.users.panix.com> - 2020-06-09 15:40 -0400
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-09 16:25 -0700
Re: What ASCII Should Have Been Thomas Koenig <tkoenig@netcologne.de> - 2020-06-10 06:52 +0000
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-10 10:22 +0000
Re: What ASCII Should Have Been Rich Alderson <news@alderson.users.panix.com> - 2020-06-10 14:26 -0400
Re: What ASCII Should Have Been Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-06-10 20:54 +0000
Re: What the DEC-20 was, not ASCII Should Have Been John Levine <johnl@taugh.com> - 2020-06-10 18:30 +0000
Re: What the DEC-20 was, not ASCII Should Have Been Rich Alderson <news@alderson.users.panix.com> - 2020-06-11 19:01 -0400
Re: What ASCII Should Have Been Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-06-10 19:35 +0000
Re: What ASCII Should Have Been Thomas Koenig <tkoenig@netcologne.de> - 2020-06-11 12:59 +0000
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-11 07:59 -0700
Re: What ASCII Should Have Been Thomas Koenig <tkoenig@netcologne.de> - 2020-06-11 17:31 +0000
Re: BATTERY RADIOS & STIRLING MOTORS robin.vowels@gmail.com - 2020-06-11 21:29 -0700
Re: BATTERY RADIOS & STIRLING MOTORS Thomas Koenig <tkoenig@netcologne.de> - 2020-06-12 07:04 +0000
Re: BATTERY RADIOS & STIRLING MOTORS Bob Eager <news0073@eager.cx> - 2020-06-12 09:06 +0000
Re: BATTERY RADIOS & STIRLING MOTORS robin.vowels@gmail.com - 2020-06-12 05:32 -0700
Re: BATTERY RADIOS & STIRLING MOTORS Gareth Evans <headstone255@yahoo.com> - 2020-06-12 14:11 +0100
Re: BATTERY RADIOS & STIRLING MOTORS => Alfred Morgan ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2020-06-12 13:41 +0000
Re: BATTERY RADIOS & STIRLING MOTORS => Alfred Morgan Bob Eager <news0073@eager.cx> - 2020-06-12 14:33 +0000
Re: BATTERY RADIOS & STIRLING MOTORS => Alfred Morgan Gareth Evans <headstone255@yahoo.com> - 2020-06-12 16:14 +0100
Re: BATTERY RADIOS & STIRLING MOTORS => Alfred Morgan Gareth Evans <headstone255@yahoo.com> - 2020-06-12 16:07 +0100
Re: BATTERY RADIOS & STIRLING MOTORS => Alfred Morgan ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2020-06-12 16:59 +0000
Re: BATTERY RADIOS & STIRLING MOTORS => Alfred Morgan Peter Flass <peter_flass@yahoo.com> - 2020-06-12 10:31 -0700
Re: BATTERY RADIOS & STIRLING MOTORS => Alfred Morgan Ahem A Rivet's Shot <steveo@eircom.net> - 2020-06-12 20:33 +0100
Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) Mike Spencer <mds@bogus.nodomain.nowhere> - 2020-06-12 17:09 -0300
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) Quadibloc <jsavard@ecn.ab.ca> - 2020-06-12 14:12 -0700
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) J. Clarke <jclarke.873638@gmail.com> - 2020-06-12 19:54 -0400
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) J. Clarke <jclarke.873638@gmail.com> - 2020-06-12 19:54 -0400
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) Mike Spencer <mds@bogus.nodomain.nowhere> - 2020-06-13 02:57 -0300
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) J. Clarke <jclarke.873638@gmail.com> - 2020-06-13 02:15 -0400
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) Gareth Evans <headstone255@yahoo.com> - 2020-06-14 13:54 +0100
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) Peter Flass <peter_flass@yahoo.com> - 2020-06-14 15:30 -0700
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) Mike Spencer <mds@bogus.nodomain.nowhere> - 2020-06-14 22:57 -0300
Re: Fun with X-raays (thread drift from BATTERY RADIOS & STIRLING...) JimP <solosam90@gmail.com> - 2020-06-14 21:00 -0500
Re: Fun with X-rays robin.vowels@gmail.com - 2020-06-14 21:12 -0700
Re: Fun with X-rays JimP <solosam90@gmail.com> - 2020-06-15 10:05 -0500
Re: Fun with X-rays Peter Flass <peter_flass@yahoo.com> - 2020-06-15 10:05 -0700
Re: Fun with X-rays Dallas <dallas@texas.usa> - 2020-06-15 13:26 -0500
Re: Fun with X-rays John Levine <johnl@taugh.com> - 2020-06-15 18:46 +0000
Re: Fun with X-rays J. Clarke <jclarke.873638@gmail.com> - 2020-06-15 19:30 -0400
Re: Fun with X-rays Dallas <dallas@texas.usa> - 2020-06-15 20:36 -0500
Re: Fun with X-rays J. Clarke <jclarke.873638@gmail.com> - 2020-06-15 22:27 -0400
Re: Fun with X-rays Bob Eager <news0073@eager.cx> - 2020-06-16 06:40 +0000
Re: Radium girls, not Fun with X-rays John Levine <johnl@taugh.com> - 2020-06-15 17:29 +0000
Re: BATTERY RADIOS & STIRLING MOTORS Peter Flass <peter_flass@yahoo.com> - 2020-06-12 07:49 -0700
Re: BATTERY RADIOS & STIRLING MOTORS robin.vowels@gmail.com - 2020-06-12 08:50 -0700
Re: What ASCII Should Have Been Bob Martin <bob.martin@excite.com> - 2020-06-12 06:07 +0000
Re: What ASCII Should Have Been Niklas Karlsson <anksil@yahoo.se> - 2020-06-14 14:50 +0000
Re: What ASCII Should Have Been "Kerr-Mudd,John" <notsaying@invalid.org> - 2020-06-14 15:01 +0000
Re: What ASCII Should Have Been J. Clarke <jclarke.873638@gmail.com> - 2020-06-14 11:36 -0400
Re: What ASCII Should Have Been Niklas Karlsson <anksil@yahoo.se> - 2020-06-14 18:03 +0000
Re: What ASCII Should Have Been usenet@only.tnx (Questor) - 2020-06-18 18:48 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-09 07:26 -0700
Re: What ASCII Should Have Been Dan Espen <dan1espen@gmail.com> - 2020-06-09 12:02 -0400
Re: What ASCII Should Have Been Dallas <dallas@texas.usa> - 2020-06-09 11:08 -0500
Subject line evolution Ahem A Rivet's Shot <steveo@eircom.net> - 2020-06-09 17:33 +0100
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-09 11:51 -0700
Re: What ASCII Should Have Been usenet@only.tnx (Questor) - 2020-06-18 18:48 +0000
Re: fast emulators, not What ASCII Should Have Been John Levine <johnl@taugh.com> - 2020-06-09 17:43 +0000
Re: What ASCII Should Have Been usenet@only.tnx (Questor) - 2020-06-18 18:48 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-09 07:32 -0700
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-09 07:47 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-09 11:51 -0700
Re: What ASCII Should Have Been usenet@only.tnx (Questor) - 2020-06-18 18:49 +0000
Re: What ASCII Should Have Been usenet@only.tnx (Questor) - 2020-06-18 18:50 +0000
Re: What ASCII Should Have Been John Levine <johnl@taugh.com> - 2020-06-09 15:24 +0000
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-09 11:51 -0700
Re: What ASCII Should Have Been pechter@lakewoodmicro.com () - 2020-06-16 20:55 +0000
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-05 21:27 +0000
Re: What ASCII Should Have Been Dallas <dallas@texas.usa> - 2020-06-05 16:54 -0500
Re: What ASCII Should Have Been scott@slp53.sl.home (Scott Lurndal) - 2020-06-05 22:44 +0000
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-05 23:18 +0000
Re: What ASCII Should Have Been robin.vowels@gmail.com - 2020-06-03 16:37 -0700
Re: What ASCII Should Have Been Bob Eager <news0073@eager.cx> - 2020-06-04 05:23 +0000
Re: What ASCII Should Have Been robin.vowels@gmail.com - 2020-06-03 16:35 -0700
Re: What ASCII Should Have Been Andy Walker <anw@cuboid.co.uk> - 2020-06-04 11:31 +0100
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-04 07:05 -0700
Re: What ASCII Should Have Been Peter Flass <peter_flass@yahoo.com> - 2020-06-04 07:06 -0700
Re: What ASCII Should Have Been scott@slp53.sl.home (Scott Lurndal) - 2020-06-04 15:23 +0000
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-06-04 09:38 -0700
Re: What ASCII Should Have Been Ahem A Rivet's Shot <steveo@eircom.net> - 2020-06-04 17:31 +0100
Re: What ASCII Should Have Been Andy Burns <usenet@andyburns.uk> - 2020-06-09 10:25 +0100
Re: What ASCII Should Have Been Quadibloc <jsavard@ecn.ab.ca> - 2020-07-05 16:35 -0700
Page 10 of 10 — ← Prev page 1 … 8 9 [10]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-06-09 11:51 -0700 |
| Message-ID | <968772549.613420929.488116.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #211844 |
Quadibloc <jsavard@ecn.ab.ca> wrote: > On Sunday, June 7, 2020 at 1:09:00 PM UTC-6, Thomas Koenig wrote: > >> Let's look at argument size mismatches that "worked" on >> little-endian systems like a VAX. Should IBM have changed their >> compilers for big-endian MVS systems to match what the VAX did? > > I will admit no. For one thing, the 7090 was not a VAX, and it was also big- > endian. Instead, Digital should have made sure that its compilers for the VAX > would preserve all the quirks of their compilers for the PDP-10, since they > discontinued the DECsystem-20 in favor of the VAX. > > Since the PDP-10 was a 36-bit big-endian system, and the VAX a 32-bit little- > endian system, however, one will have to forgive some limitations. Instead, they > should simply have done what IBM did with the 360: allow the VAX to run the > PDP-10 compilers and the code they generate in emulation mode. > > John Savard > Plus, as has been pointed out, the VAX people didn’t give a flying fig what the rest of DEC did. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | pechter@lakewoodmicro.com () |
|---|---|
| Date | 2020-06-16 20:55 +0000 |
| Message-ID | <rcbbjh$5l9$1@pechter.eternal-september.org> |
| In reply to | #211844 |
In article <53977137-c62f-40f8-bbdf-49d1bec91dd6o@googlegroups.com>, Quadibloc <jsavard@ecn.ab.ca> wrote: >On Sunday, June 7, 2020 at 1:09:00 PM UTC-6, Thomas Koenig wrote: > >> Let's look at argument size mismatches that "worked" on >> little-endian systems like a VAX. Should IBM have changed their >> compilers for big-endian MVS systems to match what the VAX did? > >I will admit no. For one thing, the 7090 was not a VAX, and it was also big- >endian. Instead, Digital should have made sure that its compilers for the VAX >would preserve all the quirks of their compilers for the PDP-10, since they >discontinued the DECsystem-20 in favor of the VAX. > >Since the PDP-10 was a 36-bit big-endian system, and the VAX a 32-bit little- >endian system, however, one will have to forgive some limitations. >Instead, they >should simply have done what IBM did with the 360: allow the VAX to run the >PDP-10 compilers and the code they generate in emulation mode. > >John Savard Too much political infighting betweeen the separate product lines. In Field Service I knew the PDP10 folks didn't think too much of the PDP11/Vax folks -- and after the Jupiter cqancellation it got pretty ugly. From what I heard in the field, there were fights over resources and the PDP10 was resurrected with further updates and support after being "DECommitted." No love was lost between the 10 and 20 folks who never felt that the VAX was a good enough timesharing box. It took a while and the move away from DZ11s for the DEC Vax hardware to expand up to the number of timesharing users. Clustering was an important part of the move up which happened in the customer environments after the late 80's. Many of the DEC customers who had 10's and 20's moved to cheaper Unix boxes so they had more than a sole source. Compuserve and other big users found KL alternatives from System Concepts and Foonly and others. The PDP11/70 guys had more ease of migration to the Vax and most of them moved with the times. The PDP10 folks had a lot of custom written software to deal with that was already in production. A tool like VEST that would do PDP10 to Vax translation or (like what they had in Alpha) compiler compatibility would've been amazing but the two PDP10 OS's were too different to migrate to VMS. RTEM was an RT11 emulator to allow RT11 software to be built and run under VMS. Some similar tool for the PDP10 systems would've been nice -- but it was a very different machine and until the 8650 probably wouldn't have performed well. Bill
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0073@eager.cx> |
|---|---|
| Date | 2020-06-05 21:27 +0000 |
| Message-ID | <hjvrmqF9tefU2@mid.individual.net> |
| In reply to | #211786 |
On Fri, 05 Jun 2020 18:27:41 +0000, Thomas Koenig wrote: > There were a few dodgy features that were indeed removed from the > Fortran standards, but most compilers retain them anyway. But many > people wrote illegal code in the day, and that can be aproblem. Indeed. There was once (actually, still is) a large multinational company who invented a language for building applications on their system. Thew compiler was written in COBOL. The run time system was written in COBOL (using interpretive code). The core of the system was written in COBOL. The whole thing was fast, except for the interpreted code. I was brought in to write a native code compiler (in fact, I did it for two very different machine architectures). It all worked wel, except...the language was not defined by its manual, but by what the compiler accepted. The original writer had no real idea about parsing, and it accepted some very weird stuff - which people used. It ended up that my compiler had to do the same, just because of the large installed base. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | Dallas <dallas@texas.usa> |
|---|---|
| Date | 2020-06-05 16:54 -0500 |
| Message-ID | <rbeeua$706$1@dont-email.me> |
| In reply to | #211796 |
On 6/5/2020 4:27 PM, Bob Eager wrote: > On Fri, 05 Jun 2020 18:27:41 +0000, Thomas Koenig wrote: > >> There were a few dodgy features that were indeed removed from the >> Fortran standards, but most compilers retain them anyway. But many >> people wrote illegal code in the day, and that can be aproblem. > > Indeed. There was once (actually, still is) a large multinational company > who invented a language for building applications on their system. Thew > compiler was written in COBOL. The run time system was written in COBOL > (using interpretive code). The core of the system was written in COBOL. > > The whole thing was fast, except for the interpreted code. I was brought > in to write a native code compiler (in fact, I did it for two very > different machine architectures). > > It all worked wel, except...the language was not defined by its manual, > but by what the compiler accepted. The original writer had no real idea > about parsing, and it accepted some very weird stuff - which people used. > It ended up that my compiler had to do the same, just because of the > large installed base. > > > I created a language once like that. It just grew organically to whatever suited me at the time. No one used it but me, and the output was the same code in a different, but well-defined language. I guess today we would call it a transpiler. I took great pains to make sure all the "comments" in my language were preserved during the translation and that the output was respectably formatted. I did archive the output code into production. The output code from my transpiler was the assembly language for the T.I 9900 CPU The programs I wrote in it were device drivers. I just got bored of writing them in assembly, so I invented my own language. I even experimented with right-hand side from left-hand side assignment syntax like 1 + 2 => variable as well as the more traditional variable <= 1 + 2 I don't remember actually using the right-hand side assigned from left-hand side variation too often though. It was just something I wanted in my language. I could just drop actual assembly code in anywhere if I did not have a high level way to express it and the transpiler would just pass it through to the output.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2020-06-05 22:44 +0000 |
| Message-ID | <iVzCG.307008$Ff6.163853@fx40.iad> |
| In reply to | #211796 |
Bob Eager <news0073@eager.cx> writes: >On Fri, 05 Jun 2020 18:27:41 +0000, Thomas Koenig wrote: > >> There were a few dodgy features that were indeed removed from the >> Fortran standards, but most compilers retain them anyway. But many >> people wrote illegal code in the day, and that can be aproblem. > >Indeed. There was once (actually, still is) a large multinational company >who invented a language for building applications on their system. Thew >compiler was written in COBOL. The run time system was written in COBOL >(using interpretive code). The core of the system was written in COBOL. Was it this? https://en.wikipedia.org/wiki/LINC_4GL
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0073@eager.cx> |
|---|---|
| Date | 2020-06-05 23:18 +0000 |
| Message-ID | <hk025sF9tefU3@mid.individual.net> |
| In reply to | #211800 |
On Fri, 05 Jun 2020 22:44:30 +0000, Scott Lurndal wrote: > Bob Eager <news0073@eager.cx> writes: >>On Fri, 05 Jun 2020 18:27:41 +0000, Thomas Koenig wrote: >> >>> There were a few dodgy features that were indeed removed from the >>> Fortran standards, but most compilers retain them anyway. But many >>> people wrote illegal code in the day, and that can be aproblem. >> >>Indeed. There was once (actually, still is) a large multinational >>company who invented a language for building applications on their >>system. Thew compiler was written in COBOL. The run time system was >>written in COBOL (using interpretive code). The core of the system was >>written in COBOL. > > Was it this? > > https://en.wikipedia.org/wiki/LINC_4GL No. But contractually I cannot say what it was. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | robin.vowels@gmail.com |
|---|---|
| Date | 2020-06-03 16:37 -0700 |
| Message-ID | <69316da0-6338-4307-a0eb-e66ae98af829@googlegroups.com> |
| In reply to | #211705 |
On Wednesday, June 3, 2020 at 11:08:41 PM UTC+10, Bob Eager wrote: > On Wed, 03 Jun 2020 10:40:54 +0100, Andy Walker wrote: > > > On 03/06/2020 03:46, r......@gmail.com wrote: > >> [ and ] are used by ALGOL. > > > > Yes, but at least [for the past 61 years anyway] it is not > > necessary to use "[...]". You can use "(...)" anywhere that "[...]" > > is expected [and also in place of "begin ... end", "case ... esac" and > > "if ... fi"]. Other languages may not be so "lucky". OTOH, > > as seen here, I like to use "[...]" for parenthetic remarks; easier to > > reach and type on my keyboard. > > But that is specifically ALGOL 68 - a very very different language. [ and ] have been used for ALGOL 60, and probably from Algol 58.
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0073@eager.cx> |
|---|---|
| Date | 2020-06-04 05:23 +0000 |
| Message-ID | <hjrepoFi0eU8@mid.individual.net> |
| In reply to | #211726 |
On Wed, 03 Jun 2020 16:37:37 -0700, robin.vowels wrote: > On Wednesday, June 3, 2020 at 11:08:41 PM UTC+10, Bob Eager wrote: >> On Wed, 03 Jun 2020 10:40:54 +0100, Andy Walker wrote: >> >> > On 03/06/2020 03:46, r......@gmail.com wrote: >> >> [ and ] are used by ALGOL. >> > >> > Yes, but at least [for the past 61 years anyway] it is not >> > necessary to use "[...]". You can use "(...)" anywhere that "[...]" >> > is expected [and also in place of "begin ... end", "case ... esac" >> > and "if ... fi"]. Other languages may not be so "lucky". OTOH, >> > as seen here, I like to use "[...]" for parenthetic remarks; easier >> > to reach and type on my keyboard. >> >> But that is specifically ALGOL 68 - a very very different language. > > [ and ] have been used for ALGOL 60, and probably from Algol 58. Oh, I know. But not the rest of it. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | robin.vowels@gmail.com |
|---|---|
| Date | 2020-06-03 16:35 -0700 |
| Message-ID | <5d9378a0-51a2-4832-b9da-bcab7438cd96@googlegroups.com> |
| In reply to | #211703 |
On Wednesday, June 3, 2020 at 7:40:56 PM UTC+10, Andy Walker wrote: > On 03/06/2020 03:46, r......@gmail.com wrote: > > [ and ] are used by ALGOL. > > Yes, but at least [for the past 61 years anyway] it is not > necessary to use "[...]". Yes it was and is. ALGOL language requires them. You cannot use ( ) instead. > You can use "(...)" anywhere that "[...]" > is expected [and also in place of "begin ... end", "case ... esac" > and "if ... fi"]. Other languages may not be so "lucky". OTOH, > as seen here, I like to use "[...]" for parenthetic remarks; easier > to reach and type on my keyboard.
[toc] | [prev] | [next] | [standalone]
| From | Andy Walker <anw@cuboid.co.uk> |
|---|---|
| Date | 2020-06-04 11:31 +0100 |
| Message-ID | <rbaii0$170m$1@gioia.aioe.org> |
| In reply to | #211725 |
On 04/06/2020 00:35, robin.vowels@gmail.com wrote:
[Necessity for "[...]":]
> ALGOL language requires them.
> You cannot use ( ) instead.
$ a68g -p '( () INT a = (1,2,3);
a(2) | ~, "Yes you can; see RR 9.4." + whole(a(1),0) +
"d, ""style i sub symbol""", ~ )'
Yes you can; see RR 9.4.1d, "style i sub symbol"
--
Andy Walker,
Nottingham.
[toc] | [prev] | [next] | [standalone]
| From | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| Date | 2020-06-04 07:05 -0700 |
| Message-ID | <0f7a6752-c7a8-4634-8ae6-3a05f8f8f490@googlegroups.com> |
| In reply to | #211743 |
On Thursday, June 4, 2020 at 4:31:30 AM UTC-6, Andy Walker wrote: > On 04/06/2020 00:35, robin.vowels@gmail.com wrote: > [Necessity for "[...]":] > > ALGOL language requires them. > > You cannot use ( ) instead. > > $ a68g -p '( () INT a = (1,2,3); > a(2) | ~, "Yes you can; see RR 9.4." + whole(a(1),0) + > "d, ""style i sub symbol""", ~ )' > Yes you can; see RR 9.4.1d, "style i sub symbol" For one thing, the reference may have been to the language ALGOL 60 and not Algol 68. For another, implementations of Algol 60 varied widely in the character set they used. Thus, in many implementations, keywords had to be in single quotes, like 'BEGIN' but in others this was not necessary. The Algol publication language used a *lot* of special characters not found on most computers. The card punches for an IBM computer didn't even _have_ square brackets on them, so no doubt their implementations found a way to do without square brackets. Since an ASR 33 did have square brackets, though, other computers may well have made those characters required for their implementations of Algol 60. John Savard
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-06-04 07:06 -0700 |
| Message-ID | <1991422615.612970687.962452.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #211696 |
<robin.vowels@gmail.com> wrote: > On Tuesday, June 2, 2020 at 12:25:12 PM UTC+10, Quadibloc wrote: >> I know it's too late to change now. >> >> The layout of the Model M keyboard finally got things right, with the two shift >> keys in their proper places, the back space key nicely reachable, and the Enter >> key reachable as well. >> >> However, I still long for the double-height Enter (or carriage return) key of long >> ago... >> >> and on the page >> >> http://www.quadibloc.com/comp/kyb0603.htm >> >> if you scroll right to the bottom, >> >> you will see what I think that ASCII should have been in order to avoid the need >> for ASCII with lowercase to demand a keyboard with more keys on it than a normal >> typewriter had. > > What? ASCII with lower case does not require more keys than > a "normal" typewriter. > > (And what is a "normal" typewriter anyway? > Does it mean one that uses small L for the digit 1, > etc. > Lower case ASCII requires only the use of a shift key, > just like an ordinary typewriter. > >> And yet, I allow _more_ special characters, not _less_, than we have in regular >> ASCII, by getting rid of all those control characters no one ever uses! > > ASCII NULL, CR, LF, FF etc are commonly used. But not usually typed. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2020-06-04 15:23 +0000 |
| Message-ID | <ql8CG.525301$TM6.217960@fx42.iad> |
| In reply to | #211745 |
Peter Flass <peter_flass@yahoo.com> writes: ><robin.vowels@gmail.com> wrote: >> On Tuesday, June 2, 2020 at 12:25:12 PM UTC+10, Quadibloc wrote: >>> I know it's too late to change now. >>> >>> The layout of the Model M keyboard finally got things right, with the two shift >>> keys in their proper places, the back space key nicely reachable, and the Enter >>> key reachable as well. >>> >>> However, I still long for the double-height Enter (or carriage return) key of long >>> ago... >>> >>> and on the page >>> >>> http://www.quadibloc.com/comp/kyb0603.htm >>> >>> if you scroll right to the bottom, >>> >>> you will see what I think that ASCII should have been in order to avoid the need >>> for ASCII with lowercase to demand a keyboard with more keys on it than a normal >>> typewriter had. >> >> What? ASCII with lower case does not require more keys than >> a "normal" typewriter. >> >> (And what is a "normal" typewriter anyway? >> Does it mean one that uses small L for the digit 1, >> etc. >> Lower case ASCII requires only the use of a shift key, >> just like an ordinary typewriter. >> >>> And yet, I allow _more_ special characters, not _less_, than we have in regular >>> ASCII, by getting rid of all those control characters no one ever uses! >> >> ASCII NULL, CR, LF, FF etc are commonly used. > >But not usually typed. Unless you are a programmer. (e.g. \n, \r, \f \0 in C-like languages).
[toc] | [prev] | [next] | [standalone]
| From | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| Date | 2020-06-04 09:38 -0700 |
| Message-ID | <7cdbc391-90a7-4e44-93ce-78448205f6aa@googlegroups.com> |
| In reply to | #211754 |
On Thursday, June 4, 2020 at 9:23:04 AM UTC-6, Scott Lurndal wrote: > Peter Flass <peter_flass@yahoo.com> writes: > ><robin.vowels@gmail.com> wrote: > >> ASCII NULL, CR, LF, FF etc are commonly used. > >But not usually typed. > Unless you are a programmer. (e.g. \n, \r, \f \0 in C-like languages). It's true that on an IBM PC, as opposed to when one is using a terminal to communicate with a mainframe, pressing the backspace key is not the same as sending a back space character, pressing the Tab key may not be the same as sending a tab character (although if one is using Unix, at least, it will put a tab character in a text file, because there they're used as white space), and pressing Enter is not the same as sending a carriage return character (or line feed, for Unix)... but some control characters are sent by the user. I did include the most common in the few control character positions left in my suggested revision to ASCII. John Savard
[toc] | [prev] | [next] | [standalone]
| From | Ahem A Rivet's Shot <steveo@eircom.net> |
|---|---|
| Date | 2020-06-04 17:31 +0100 |
| Message-ID | <20200604173119.b3c8d2f6a402bb9a99aac6bd@eircom.net> |
| In reply to | #211745 |
On Thu, 4 Jun 2020 07:06:32 -0700 Peter Flass <peter_flass@yahoo.com> wrote: > <robin.vowels@gmail.com> wrote: > > ASCII NULL, CR, LF, FF etc are commonly used. > > But not usually typed. I've typed CR, LF and FF quite often, the first two very often when using an ASR-33, the last to paginate text files. -- Steve O'Hara-Smith | Directable Mirror Arrays C:\>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. | http://www.sohara.org/
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2020-06-09 10:25 +0100 |
| Message-ID | <hk92seFrutdU1@mid.individual.net> |
| In reply to | #211756 |
Ahem A Rivet's Shot wrote: > I've typed CR, LF and FF quite often ^Jstty sane^J
[toc] | [prev] | [next] | [standalone]
| From | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| Date | 2020-07-05 16:35 -0700 |
| Message-ID | <54a9f334-73b0-42e5-bbd4-bf878f3a8e92o@googlegroups.com> |
| In reply to | #211682 |
On my page at http://www.quadibloc.com/comp/ascint.htm at the very bottom of the page I show a _further_ modification of my scheme for an "improved" ASCII that is suited to the 44-key keyboard... by making it possible to support alphabets with a limited number of letters beyond the 26 letters of the unadorned Latin alphabet. Not enough to _directly_ support Armenian, or even Cyrillic... but with three extra letters, at least a German keyboard is possible. John Savard
[toc] | [prev] | [standalone]
Page 10 of 10 — ← Prev page 1 … 8 9 [10]
Back to top | Article view | alt.folklore.computers
csiph-web