Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.unix.shell > #24808 > unrolled thread
| Started by | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| First post | 2024-03-29 01:14 +0000 |
| Last post | 2024-10-01 22:22 +0000 |
| Articles | 20 on this page of 736 — 47 participants |
Back to article view | Back to comp.unix.shell
Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-29 01:14 +0000
Re: Command Languages Versus Programming Languages candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-03-29 03:10 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-29 10:37 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-29 20:59 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 00:14 +0100
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 00:45 +0100
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-29 17:03 -0700
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 01:06 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-29 23:51 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-29 17:08 -0700
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-30 01:12 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-29 18:15 -0700
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-03-30 01:21 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 01:30 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-30 01:15 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-29 17:01 -0700
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 01:49 +0100
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-29 18:00 -0700
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-31 20:47 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 00:22 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-30 05:54 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-03-29 09:55 +0000
Re: Command Languages Versus Programming Languages Josef Möllers <josef@invalid.invalid> - 2024-03-29 12:10 +0100
Re: Command Languages Versus Programming Languages Richard Kettlewell <invalid@invalid.invalid> - 2024-03-29 11:40 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-03-29 12:02 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-03-29 17:09 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-03-29 17:18 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-03-29 17:25 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-03-30 10:16 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 11:35 +0100
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-03-30 18:10 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-01 08:31 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-03-30 19:27 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-03-29 08:44 -0700
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-03-29 16:02 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-03-29 09:10 -0700
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-03-29 17:13 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-03-29 17:20 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-03-29 17:58 +0000
Re: Command Languages Versus Programming Languages "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2024-03-29 14:51 -0400
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-03-29 16:38 -0300
Re: Command Languages Versus Programming Languages "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2024-03-29 18:32 -0400
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 00:14 +0100
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-03-30 10:19 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-03-30 18:46 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-01 08:32 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-04-01 06:49 -0300
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-01 14:47 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-01 18:25 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-04-01 21:26 -0300
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-02 00:57 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-01 18:18 -0700
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-02 03:01 +0000
Re: Command Languages Versus Programming Languages James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-04-02 05:28 -0400
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-03 00:25 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-04-02 15:20 -0300
Re: Command Languages Versus Programming Languages gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-02 18:58 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-04-02 18:59 +0000
Re: Command Languages Versus Programming Languages "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-04-02 22:05 +0200
Too much? (Was: Command Languages Versus Programming Languages) gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-02 20:16 +0000
Re: Too much? (Was: Command Languages Versus Programming Languages) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-02 20:20 +0000
Re: Too much? (Was: Command Languages Versus Programming Languages) gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-02 20:36 +0000
Re: Too much? (Was: Command Languages Versus Programming Languages) David Brown <david.brown@hesbynett.no> - 2024-04-03 09:38 +0200
Re: Too much? (Was: Command Languages Versus Programming Languages) James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-04-03 19:06 -0400
Football (Was: Too much? (Was: Command Languages Versus Programming Languages)) gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-03 23:22 +0000
Re: Too much? (Was: Command Languages Versus Programming Languages) Chris Elvidge <chris@mshome.net> - 2024-04-04 14:50 +0100
Re: Too much? (Was: Command Languages Versus Programming Languages) Muttley@dastardlyhq.com - 2024-04-04 14:10 +0000
Re: Too much? (Was: Command Languages Versus Programming Languages) David Brown <david.brown@hesbynett.no> - 2024-04-04 21:47 +0200
Re: Too much? (Was: Command Languages Versus Programming Languages) Mister Johnson <root@example.net> - 2024-04-04 21:15 +0000
Re: Command Languages Versus Programming Languages James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-04-02 19:15 -0400
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-03 00:23 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-04-03 07:18 -0300
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-02 16:18 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-02 16:33 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-03 00:23 +0000
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-04-03 09:50 +0200
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-03 07:53 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-03 07:53 -0700
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-03 09:00 -0700
Re: Command Languages Versus Programming Languages Richard Kettlewell <invalid@invalid.invalid> - 2024-04-03 17:16 +0100
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-04 08:13 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-04 23:29 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-05 09:17 +0000
Re: Command Languages Versus Programming Languages candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-05 12:40 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-05 15:09 +0000
Re: Command Languages Versus Programming Languages candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-06 01:10 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-05 23:11 +0000
Re: Command Languages Versus Programming Languages Alan Bawden <alan@csail.mit.edu> - 2024-04-05 19:35 -0400
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-06 00:25 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-08 08:20 -0700
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-08 22:14 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-08 15:58 -0700
Re: Command Languages Versus Programming Languages Richard Kettlewell <invalid@invalid.invalid> - 2024-04-09 08:47 +0100
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-09 10:07 +0200
Re: Command Languages Versus Programming Languages Richard Kettlewell <invalid@invalid.invalid> - 2024-04-09 18:57 +0100
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-04-09 10:11 +0200
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-09 08:38 +0000
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-04-09 15:22 +0200
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-10 00:32 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-10 01:35 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-08 23:02 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-06 01:01 +0000
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-04-06 15:44 +0200
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-06 15:03 +0000
Re: Command Languages Versus Programming Languages candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-06 01:10 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-06 09:00 +0000
Re: Command Languages Versus Programming Languages Alan Bawden <alan@csail.mit.edu> - 2024-04-07 06:04 -0400
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-08 07:47 +0000
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-04-08 14:35 +0200
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-08 14:33 +0000
Words to the wise (Was: Command Languages Versus Programming Languages) gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-08 15:20 +0000
Re: Words to the wise (Was: Command Languages Versus Programming Languages) Muttley@dastardlyhq.com - 2024-04-08 15:22 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-08 19:32 +0000
Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-08 19:44 +0000
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-09 09:24 +0200
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) D <nospam@example.net> - 2024-04-09 10:39 +0200
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-09 15:30 +0000
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-09 21:48 +0200
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-09 20:20 +0000
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-10 00:31 +0000
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) Mister Johnson <root@example.net> - 2024-04-10 10:37 +0000
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) Chris Elvidge <chris@mshome.net> - 2024-04-10 11:41 +0100
Re: Phrases that should be banned on Usenet (Was: Command Languages Versus Programming Languages) candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-10 15:40 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-09 07:45 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-09 07:57 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-09 10:02 +0200
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-04-09 15:01 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-09 15:09 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-04-09 15:30 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-09 08:40 -0700
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-09 16:01 +0000
[meta] Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-08 14:00 +0200
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-10 00:36 -0700
Re: Command Languages Versus Programming Languages gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-10 12:05 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-05 18:30 +0200
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-05 20:47 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-05 23:08 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-06 18:57 +0200
Re: Command Languages Versus Programming Languages Andy Walker <anw@cuboid.co.uk> - 2024-04-06 19:32 +0100
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-06 23:54 +0200
Re: Command Languages Versus Programming Languages Andy Walker <anw@cuboid.co.uk> - 2024-04-07 14:43 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-07 21:05 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-08 14:53 +0200
Re: Command Languages Versus Programming Languages Andy Walker <anw@cuboid.co.uk> - 2024-04-10 10:10 +0100
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-10 14:43 +0200
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-10 19:03 +0200
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-07 14:45 -0700
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-08 14:11 +0200
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-04-07 15:47 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-06 15:07 -0700
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-06 22:57 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-07 01:31 +0200
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-07 01:47 +0200
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-06 23:57 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-06 20:41 -0700
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-06 08:58 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-06 23:49 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-04-08 07:44 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-08 22:16 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-06 18:49 +0200
Re: Command Languages Versus Programming Languages Sebastian <sebastian@here.com.invalid> - 2024-08-06 08:04 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-06 23:34 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-07 13:43 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-08-08 07:33 +0000
Re: Command Languages Versus Programming Languages Bozo User <anthk@disroot.org> - 2024-09-30 20:04 +0000
Re: Command Languages Versus Programming Languages Andreas Eder <a_eder_muc@web.de> - 2024-08-08 17:25 +0200
Trading insults about Lisp coding styles (Was: Command Languages Versus Programming Languages) gazelle@shell.xmission.com (Kenny McCormack) - 2024-08-08 16:05 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-08 23:41 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-09 00:07 +0000
Re: Command Languages Versus Programming Languages Sebastian <sebastian@here.com.invalid> - 2024-08-25 07:32 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-25 07:48 +0000
Re: Command Languages Versus Programming Languages Sebastian <sebastian@here.com.invalid> - 2024-08-26 16:13 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 21:31 +0000
Re: Command Languages Versus Programming Languages Sebastian <sebastian@here.com.invalid> - 2024-08-27 03:15 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 04:44 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-08-27 19:56 -0300
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 23:26 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-08-27 21:08 -0300
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-28 00:09 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-27 19:10 -0700
Re: Command Languages Versus Programming Languages Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-18 00:34 +0100
OT: "All Rights Reserved" misleading nonsense (was: Re: Command Languages Versus Programming Languages) Nuno Silva <nunojsilva@invalid.invalid> - 2025-10-18 09:28 +0100
Re: OT: "All Rights Reserved" misleading nonsense yeti <yeti@tilde.institute> - 2025-10-18 10:00 +0042
Re: OT: "All Rights Reserved" misleading nonsense (was: Re: Command Languages Versus Programming Languages) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-18 20:26 +0000
Re: OT: "All Rights Reserved" misleading nonsense Nuno Silva <nunojsilva@invalid.invalid> - 2025-10-19 11:30 +0100
Re: OT: "All Rights Reserved" misleading nonsense Jim <jim.beard@verizon.net> - 2025-10-19 14:43 +0000
Re: OT: "All Rights Reserved" misleading nonsense Brian Patrie <bpatrie@bellsouth.spamisicky.net> - 2025-10-21 15:49 -0500
Re: OT: "All Rights Reserved" misleading nonsense Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-21 21:58 +0000
Re: OT: "All Rights Reserved" misleading nonsense Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-10-22 11:40 +0200
Re: OT: "All Rights Reserved" misleading nonsense Nuno Silva <nunojsilva@invalid.invalid> - 2025-10-22 23:13 +0100
Re: OT: "All Rights Reserved" misleading nonsense Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-10-23 04:56 +0200
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-10-17 17:13 -0700
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-04-03 18:30 +0200
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-03 10:19 -0700
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-04-03 21:33 +0200
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-03 12:58 -0700
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-01 21:41 +0000
Re: Command Languages Versus Programming Languages Andreas Eder <a_eder_muc@web.de> - 2024-04-01 17:11 +0200
Re: Command Languages Versus Programming Languages Christian Weisgerber <naddy@mips.inka.de> - 2024-03-29 18:12 +0000
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-03-30 19:32 +0100
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-03-30 20:19 +0000
Re: Command Languages Versus Programming Languages Bozo User <anthk@disroot.org> - 2024-09-30 20:04 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-03-29 17:12 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-03-29 08:09 -0300
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-29 12:36 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-29 21:06 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-03-29 21:24 -0300
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-30 01:11 +0000
Re: Command Languages Versus Programming Languages Johanne Fairchild <jfairchild@tudado.org> - 2024-03-29 21:17 -0300
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-30 11:28 +0100
Re: Command Languages Versus Programming Languages Christian Weisgerber <naddy@mips.inka.de> - 2024-03-30 13:37 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-03-30 19:25 +0000
Re: Command Languages Versus Programming Languages Christian Weisgerber <naddy@mips.inka.de> - 2024-03-30 21:48 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-01 11:15 -0700
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-04-01 19:42 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-01 13:25 -0700
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-02 00:20 +0000
Re: Command Languages Versus Programming Languages James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-04-02 05:13 -0400
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-01 13:44 -0700
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-01 14:30 -0700
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-04-01 22:40 +0000
Re: Command Languages Versus Programming Languages candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-02 15:30 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-02 08:43 -0700
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-04-02 16:09 +0000
Re: Command Languages Versus Programming Languages candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-02 18:50 +0000
Re: Command Languages Versus Programming Languages Richard Kettlewell <invalid@invalid.invalid> - 2024-04-03 15:45 +0100
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-04-03 16:56 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-01 15:56 -0700
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-02 00:19 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-01 21:43 +0000
Re: Command Languages Versus Programming Languages Javier <invalid@invalid.invalid> - 2024-04-07 00:01 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-07 02:02 +0000
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-06 20:46 -0700
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-12 15:55 +0200
Re: Command Languages Versus Programming Languages Bozo User <anthk@disroot.org> - 2024-09-30 20:04 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-30 21:04 +0000
Re: Command Languages Versus Programming Languages usuario <anthk@disroot.org> - 2024-10-01 20:18 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-02 07:10 +0000
Re: Command Languages Versus Programming Languages usuario <anthk@disroot.org> - 2024-10-02 12:52 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-02 16:00 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-09 22:25 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-10 08:38 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-10 16:09 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-10 15:34 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-10 17:55 +0100
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-10-10 19:14 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-10 21:31 +0100
Re: Command Languages Versus Programming Languages Bart <bc@freeuk.com> - 2024-10-11 00:09 +0100
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-11 15:47 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-11 15:15 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-11 15:45 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-11 15:59 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-11 16:28 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-12 08:39 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-12 13:53 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-10-12 14:50 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-10-12 15:32 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-10-12 15:51 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-12 16:36 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-13 08:18 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-13 13:43 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-13 14:54 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-13 15:30 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-13 16:02 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-13 20:15 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-14 08:25 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-14 13:38 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-14 14:47 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-10-14 14:53 +0000
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-10-14 17:27 +0200
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-13 21:09 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-13 21:08 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-10-13 15:08 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-13 15:52 +0000
Re: Command Languages Versus Programming Languages Bart <bc@freeuk.com> - 2024-10-13 17:20 +0100
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-13 20:29 +0000
Re: Command Languages Versus Programming Languages Bart <bc@freeuk.com> - 2024-10-14 01:20 +0100
Re: On overly rigid definitions (was Re: Command Languages Versus Programming Languages) cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-14 00:58 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-10-13 15:02 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-10-13 16:31 +0000
Re: Command Languages Versus Programming Languages Bart <bc@freeuk.com> - 2024-10-13 20:06 +0100
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-10-13 20:30 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-10-11 16:37 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-11 19:01 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-12 08:40 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-11 20:58 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-12 08:42 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-12 14:37 +0100
Re: Command Languages Versus Programming Languages Christian Weisgerber <naddy@mips.inka.de> - 2024-10-12 17:49 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-13 08:20 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-13 21:25 +0100
Re: Command Languages Versus Programming Languages Bart <bc@freeuk.com> - 2024-10-12 20:50 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-12 21:25 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-13 08:22 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-13 20:33 +0000
Re: Command Languages Versus Programming Languages Bart <bc@freeuk.com> - 2024-10-11 00:07 +0100
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-11 16:15 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-11 08:17 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-11 19:37 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-11 01:33 +0000
Re: Command Languages Versus Programming Languages Eric Pozharski <apple.universe@posteo.net> - 2024-10-12 16:39 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-13 08:19 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-10-13 14:55 +0200
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-13 21:33 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-14 08:28 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-14 11:38 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-14 11:05 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-10-14 16:04 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-10-14 15:39 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-13 20:34 +0000
Re: Command Languages Versus Programming Languages Sebastian <sebastian@here.com.invalid> - 2024-11-11 07:31 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-11 10:06 +0000
Re: Command Languages Versus Programming Languages Wolfgang Agnes <wagnes@jemoni.to> - 2024-11-11 08:28 -0300
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-11-11 16:21 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-11 20:55 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-12 10:14 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-12 09:21 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-12 10:31 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-12 09:53 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-12 15:05 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-12 15:09 +0000
Re: Command Languages Versus Programming Languages Wolfgang Agnes <wagnes@jemoni.to> - 2024-11-12 13:47 -0300
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-11 21:24 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-12 10:23 +0100
Re: Command Languages Versus Programming Languages Wolfgang Agnes <wagnes@jemoni.to> - 2024-11-12 13:50 -0300
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-12 20:29 +0000
Re: Command Languages Versus Programming Languages merlyn@stonehenge.com (Randal L. Schwartz) - 2024-11-19 18:43 -0800
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-20 04:34 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-20 08:21 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-20 11:51 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-20 11:30 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-20 16:38 +0100
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-20 16:38 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-20 17:54 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-11-20 10:03 -0800
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-21 08:18 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-11-21 07:56 -0800
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-21 14:13 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-21 16:06 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-21 08:13 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-11-21 07:58 -0800
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-20 17:50 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-21 14:40 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-21 15:07 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 13:30 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 15:41 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 15:52 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 17:18 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 17:35 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 17:43 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 17:43 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 17:17 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 17:48 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 18:12 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 18:48 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 19:05 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 19:24 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 19:46 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-11-22 18:14 +0000
Re: Command Languages Versus Programming Languages scott@slp53.sl.home (Scott Lurndal) - 2024-11-22 18:22 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 18:30 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 18:59 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 19:15 +0000
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 19:26 +0000
Re: Command Languages Versus Programming Languages cross@spitfire.i.gajendra.net (Dan Cross) - 2024-11-22 19:51 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-22 12:14 +0100
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-22 11:56 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-22 20:33 +0100
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-11-21 19:12 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-22 10:09 +0000
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-11-22 18:18 +0000
Re: Command Languages Versus Programming Languages Muttley@dastardlyhq.com - 2024-11-23 11:40 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-22 12:17 +0100
Re: Command Languages Versus Programming Languages Kaz Kylheku <643-408-1753@kylheku.com> - 2024-11-22 18:19 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-22 20:20 +0100
Re: Command Languages Versus Programming Languages Ed Morton <mortonspam@gmail.com> - 2024-11-20 05:46 -0600
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-20 12:27 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-20 21:43 +0000
Re: Command Languages Versus Programming Languages Muttley@DastartdlyHQ.org - 2024-11-21 08:15 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-21 22:05 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-22 12:47 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-22 20:41 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-11-20 16:53 +0100
Re: Command Languages Versus Programming Languages Ed Morton <mortonspam@gmail.com> - 2024-11-23 18:17 -0600
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-20 12:21 +0000
Re: Command Languages Versus Programming Languages merlyn@stonehenge.com (Randal L. Schwartz) - 2024-11-21 05:38 -0800
Re: Command Languages Versus Programming Languages Rainer Weikusat <rweikusat@talktalk.net> - 2024-11-21 17:01 +0000
Re: Command Languages Versus Programming Languages John Ames <commodorejohn@gmail.com> - 2024-04-08 07:55 -0700
Re: Command Languages Versus Programming Languages Javier <invalid@invalid.invalid> - 2024-04-08 17:54 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-08 22:21 +0000
Re: Command Languages Versus Programming Languages Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-12 15:48 +0200
I did not inhale (Was: Command Languages Versus Programming Languages) gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-12 14:13 +0000
Re: I did not inhale (Was: Command Languages Versus Programming Languages) gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-12 14:15 +0000
Re: I did not inhale (Was: Command Languages Versus Programming Languages) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-04-15 14:28 +0200
Re: I did not inhale (Was: Command Languages Versus Programming Languages) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-12 16:52 +0000
Re: I did not inhale Johanne Fairchild <jfairchild@tudado.org> - 2024-04-12 20:52 -0300
Re: I did not inhale Johanne Fairchild <jfairchild@tudado.org> - 2024-04-13 08:17 -0300
Re: I did not inhale kalevi@kolttonen.fi (Kalevi Kolttonen) - 2024-08-15 19:48 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-15 23:54 +0000
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-16 01:30 +0000
Re: Python (was Re: I did not inhale) kalevi@kolttonen.fi (Kalevi Kolttonen) - 2024-08-16 15:02 +0000
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-16 09:37 -0700
Re: Python (was Re: I did not inhale) D <nospam@example.net> - 2024-08-17 11:18 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-17 09:01 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-17 12:58 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-17 21:51 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-18 10:10 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-18 08:30 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-18 12:19 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-18 15:45 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-18 18:13 +0200
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-18 16:52 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-18 20:07 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-18 23:18 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-19 08:31 +0000
Re: Python (was Re: I did not inhale) Sebastian <sebastian@here.com.invalid> - 2024-08-25 07:50 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-25 12:32 +0200
Re: Python (was Re: I did not inhale) vallor <vallor@cultnix.org> - 2024-08-25 13:41 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-25 22:02 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-25 22:00 +0000
Re: Python (was Re: I did not inhale) Richard Kettlewell <invalid@invalid.invalid> - 2024-08-18 22:15 +0100
Re: Python (was Re: I did not inhale) gazelle@shell.xmission.com (Kenny McCormack) - 2024-08-18 08:55 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-18 09:21 +0000
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-18 16:46 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-18 20:11 +0200
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-19 04:54 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-19 09:09 +0200
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-19 17:40 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-18 23:14 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-19 09:37 +0200
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-19 10:40 +0200
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-19 12:39 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-19 14:59 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-19 17:35 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-19 15:56 +0000
Re: Python (was Re: I did not inhale) Bozo User <anthk@disroot.org> - 2024-09-30 20:04 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-19 21:09 +0200
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-20 08:52 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-20 07:21 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-20 10:15 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-21 01:00 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-20 09:44 +0200
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-20 10:27 +0200
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-20 15:09 +0200
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-20 17:20 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-21 00:59 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-21 10:07 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-21 23:42 +0000
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-19 13:14 -0700
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-19 13:30 -0700
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-20 07:22 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-19 08:45 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-19 13:03 +0200
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-19 13:28 -0700
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-19 23:43 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-19 23:03 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-20 08:57 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-20 07:22 +0000
Re: Python (was Re: I did not inhale) D <nospam@example.net> - 2024-08-20 10:25 +0200
Re: Python (was Re: I did not inhale) vallor <vallor@cultnix.org> - 2024-08-21 06:10 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-21 06:45 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-18 08:17 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-18 16:59 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-18 15:23 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-18 16:55 +0200
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-18 12:24 -0700
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-19 09:44 +0200
Re: Python (was Re: I did not inhale) kalevi@kolttonen.fi (Kalevi Kolttonen) - 2024-08-20 14:21 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-20 14:35 +0000
Re: Python (was Re: I did not inhale) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2024-08-20 14:45 +0000
Re: Python (was Re: I did not inhale) kalevi@kolttonen.fi (Kalevi Kolttonen) - 2024-08-20 16:10 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-20 21:45 +0200
Re: Python (was Re: I did not inhale) kalevi@kolttonen.fi (Kalevi Kolttonen) - 2024-08-20 20:56 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-21 09:26 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-21 07:36 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-21 11:10 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-21 10:26 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-21 17:27 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-21 15:40 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-21 21:15 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-22 07:42 +0000
Re: Python (was Re: I did not inhale) D <nospam@example.net> - 2024-08-22 09:52 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-22 08:18 +0000
Re: Python (was Re: I did not inhale) D <nospam@example.net> - 2024-08-22 15:11 +0200
Re: Python (was Re: I did not inhale) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2024-08-22 13:58 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-22 14:17 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-22 11:09 +0200
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-22 10:10 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-22 08:21 +0000
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-26 08:33 -0700
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-26 17:59 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 21:35 +0000
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-26 15:51 -0700
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 02:50 +0000
Re: Python (was Re: I did not inhale) Sebastian <sebastian@here.com.invalid> - 2024-08-27 03:21 +0000
Re: Python (was Re: I did not inhale) Richard Kettlewell <invalid@invalid.invalid> - 2024-08-27 09:39 +0100
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-27 11:26 +0100
Re: Python (was Re: I did not inhale) Richard Kettlewell <invalid@invalid.invalid> - 2024-08-27 13:46 +0100
Re: Python (was Re: I did not inhale) Sebastian <sebastian@here.com.invalid> - 2024-08-28 02:53 +0000
Re: Python (was Re: I did not inhale) scott@slp53.sl.home (Scott Lurndal) - 2024-08-28 13:57 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-27 15:10 +0200
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-27 15:18 +0100
Re: Python (was Re: I did not inhale) Andy Walker <anw@cuboid.co.uk> - 2024-08-28 23:07 +0100
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-27 08:03 -0700
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-27 18:08 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-27 20:46 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 21:40 +0000
Re: Python (was Re: I did not inhale) Sebastian <sebastian@here.com.invalid> - 2024-08-28 03:19 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-28 12:45 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-28 22:49 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 21:34 +0000
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-27 14:49 -0700
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 23:28 +0000
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-27 19:10 -0700
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-28 05:30 +0000
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-28 13:29 -0700
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-28 23:02 +0000
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-28 17:23 -0700
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-29 01:19 +0000
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-28 19:19 -0700
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-30 23:52 +0000
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-30 21:37 -0700
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-30 21:39 -0700
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-29 14:05 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-30 23:49 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-31 17:06 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-03 00:09 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-09-03 10:46 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-03 21:56 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-09-04 09:30 +0200
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-29 14:01 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-29 23:03 +0000
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-29 16:57 -0700
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-30 02:55 +0000
Re: Python (was Re: I did not inhale) vallor <vallor@cultnix.org> - 2024-08-30 14:01 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-30 10:01 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-28 17:48 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-28 17:43 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-28 20:48 +0200
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-28 20:27 +0100
Re: Python (was Re: I did not inhale) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-28 13:37 -0700
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-28 21:44 +0100
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-28 23:44 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-28 22:49 +0000
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-29 00:21 +0100
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-29 01:16 +0000
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-29 11:49 +0100
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-29 13:31 +0200
Re: Python (was Re: I did not inhale) Ben Bacarisse <ben@bsb.me.uk> - 2024-08-29 13:50 +0100
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-29 14:24 +0200
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-29 08:52 -0700
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-29 21:27 +0200
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-30 08:14 -0700
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-30 18:42 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-30 19:20 +0000
Re: Python (was Re: I did not inhale) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-14 10:16 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-09-14 09:25 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-09-15 21:43 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-29 22:57 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-30 11:38 +0200
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-30 08:28 -0700
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-30 18:54 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-30 23:42 +0000
Re: Python (was Re: I did not inhale) candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-09-07 18:30 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-07 22:48 +0000
Re: Python (was Re: I did not inhale) candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-09-26 18:00 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-26 20:36 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-09-27 08:03 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-29 07:28 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-29 14:30 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-29 16:19 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-29 21:29 +0200
Re: Python (was Re: I did not inhale) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-29 18:44 +0200
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-29 21:36 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-30 19:17 +0000
Re: Python (was Re: I did not inhale) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-14 09:59 +0200
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-09-15 21:47 +0200
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-09-16 07:27 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-30 02:53 +0000
Re: Python (was Re: I did not inhale) scott@slp53.sl.home (Scott Lurndal) - 2024-08-30 14:33 +0000
Re: Python (was Re: I did not inhale) D <nospam@example.net> - 2024-08-30 23:36 +0200
Re: Python (was Re: I did not inhale) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-14 10:06 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-14 09:34 +0000
Re: Python (was Re: I did not inhale) scott@slp53.sl.home (Scott Lurndal) - 2024-09-14 19:10 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-14 22:25 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-09-15 09:06 +0000
Re: Python (was Re: I did not inhale) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-16 17:28 +0200
Re: Python (was Re: I did not inhale) Bozo User <anthk@disroot.org> - 2024-09-30 20:04 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-30 22:08 +0000
Re: Python (was Re: I did not inhale) scott@slp53.sl.home (Scott Lurndal) - 2024-09-15 15:51 +0000
Re: Python (was Re: I did not inhale) D <nospam@example.net> - 2024-09-15 21:55 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-15 21:32 +0000
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-15 15:54 +0000
Re: Python (was Re: I did not inhale) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-16 17:30 +0200
Re: Python (was Re: I did not inhale) Sebastian <sebastian@here.com.invalid> - 2024-08-28 02:48 +0000
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-28 08:25 -0700
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-28 16:41 +0100
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-28 18:23 +0200
Re: Python (was Re: I did not inhale) Richard Kettlewell <invalid@invalid.invalid> - 2024-08-28 16:41 +0100
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-26 23:51 +0100
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 02:49 +0000
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-26 23:32 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-22 09:02 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-22 12:47 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-23 00:19 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-23 09:19 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-23 08:29 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-23 12:04 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-23 22:52 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-23 13:36 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-21 07:38 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-21 11:11 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-21 23:43 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-22 13:00 +0200
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-22 13:30 +0200
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-22 15:28 +0000
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-22 16:56 +0100
Re: Python (was Re: I did not inhale) scott@slp53.sl.home (Scott Lurndal) - 2024-08-22 16:31 +0000
Re: Python (was Re: I did not inhale) Bart <bc@freeuk.com> - 2024-08-22 17:55 +0100
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-22 17:38 +0000
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-22 17:48 +0000
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-22 17:36 +0000
Re: Python (was Re: I did not inhale) scott@slp53.sl.home (Scott Lurndal) - 2024-08-22 17:47 +0000
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-22 20:28 +0200
Re: Python (was Re: I did not inhale) "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-08-22 20:28 +0200
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-22 18:54 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-23 00:15 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-23 09:33 +0200
Re: Python (was Re: I did not inhale) Bozo User <anthk@disroot.org> - 2024-09-30 20:04 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-30 22:10 +0000
Re: Python (was Re: I did not inhale) Muttley@dastardlyhq.com - 2024-08-21 07:27 +0000
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-21 11:15 +0200
Re: Python (was Re: I did not inhale) John Ames <commodorejohn@gmail.com> - 2024-08-21 08:37 -0700
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-21 21:18 +0200
Re: Python (was Re: I did not inhale) Nuno Silva <nunojsilva@invalid.invalid> - 2024-08-25 16:32 +0100
Re: Python (was Re: I did not inhale) David Brown <david.brown@hesbynett.no> - 2024-08-25 18:41 +0200
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-25 21:59 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-21 01:05 +0000
Re: Python (was Re: I did not inhale) kalevi@kolttonen.fi (Kalevi Kolttonen) - 2024-08-21 08:45 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-21 23:42 +0000
Re: Python (was Re: I did not inhale) kalevi@kolttonen.fi (Kalevi Kolttonen) - 2024-08-16 14:57 +0000
Re: Python (was Re: I did not inhale) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-16 23:27 +0000
Re: Python (was Re: I did not inhale) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-17 01:01 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-13 21:54 +0000
on Perl (was: Command Languages Versus Programming Languages) Javier <invalid@invalid.invalid> - 2024-04-14 20:41 +0000
Re: on Perl (was: Command Languages Versus Programming Languages) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-14 22:41 +0000
Re: on Perl (was: Command Languages Versus Programming Languages) Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-04-15 12:43 +0000
Re: on Perl (was: Command Languages Versus Programming Languages) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-15 22:12 +0000
Re: on Perl (was: Command Languages Versus Programming Languages) John Ames <commodorejohn@gmail.com> - 2024-04-15 15:29 -0700
Re: on Perl (was: Command Languages Versus Programming Languages) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-15 22:58 +0000
Re: on Perl (was: Command Languages Versus Programming Languages) David Brown <david.brown@hesbynett.no> - 2024-04-16 10:14 +0200
Re: on Perl (was: Command Languages Versus Programming Languages) Muttley@dastardlyhq.com - 2024-04-16 08:35 +0000
Re: on Perl (was: Command Languages Versus Programming Languages) David Brown <david.brown@hesbynett.no> - 2024-04-16 11:35 +0200
Re: on Perl Christian Weisgerber <naddy@mips.inka.de> - 2024-04-16 10:58 +0000
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-16 14:00 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-16 14:51 +0000
Re: on Perl candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-16 15:10 +0000
Re: on Perl Muttley@dastardlyhq.com - 2024-04-16 15:42 +0000
Re: on Perl Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-17 02:44 +0000
Re: on Perl Andreas Eder <a_eder_muc@web.de> - 2024-04-17 07:34 +0200
Re: on Perl Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-17 06:44 +0000
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-17 11:27 +0200
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-17 07:55 -0700
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-17 12:19 -0700
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-17 21:52 +0200
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-17 13:39 -0700
Re: on Perl Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-18 04:18 +0000
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-18 10:30 +0200
Re: on Perl Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-18 08:36 +0000
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-18 11:31 +0200
Re: on Perl Richard Harnden <richard.nospam@gmail.invalid> - 2024-04-23 14:09 +0100
Back and forth (Was: on Perl) gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-23 14:09 +0000
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-24 10:04 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-16 14:49 +0000
Re: on Perl scott@slp53.sl.home (Scott Lurndal) - 2024-04-16 15:01 +0000
Re: on Perl Muttley@dastardlyhq.com - 2024-04-16 15:26 +0000
Re: on Perl Chris Elvidge <chris@mshome.net> - 2024-04-16 16:42 +0100
Re: on Perl Muttley@dastardlyhq.com - 2024-04-16 15:43 +0000
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-16 08:49 -0700
Re: on Perl Muttley@dastardlyhq.com - 2024-04-16 15:51 +0000
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-16 08:59 -0700
Re: on Perl Muttley@dastardlyhq.com - 2024-04-16 16:13 +0000
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-16 09:18 -0700
Re: on Perl Muttley@dastardlyhq.com - 2024-04-17 08:22 +0000
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-17 07:59 -0700
Re: on Perl Muttley@dastardlyhq.com - 2024-04-17 16:15 +0000
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-17 09:55 -0700
Re: on Perl D <nospam@example.net> - 2024-04-17 23:05 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-18 07:35 +0000
Re: on Perl D <nospam@example.net> - 2024-04-18 11:28 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-18 15:37 +0000
Re: on Perl D <nospam@example.net> - 2024-04-18 20:59 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-19 08:57 +0000
Re: on Perl D <nospam@example.net> - 2024-04-19 22:40 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-20 08:58 +0000
Re: on Perl D <nospam@example.net> - 2024-04-20 12:40 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-20 10:52 +0000
Re: on Perl D <nospam@example.net> - 2024-04-20 21:00 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-18 07:33 +0000
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-18 10:16 -0700
Re: on Perl Muttley@dastardlyhq.com - 2024-04-19 08:57 +0000
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-19 16:08 -0700
Re: on Perl gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-20 01:48 +0000
Re: on Perl John Ames <commodorejohn@gmail.com> - 2024-04-24 08:36 -0700
Re: on Perl Muttley@dastardlyhq.com - 2024-04-20 08:59 +0000
Re: on Perl gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-16 18:11 +0000
Re: on Perl Muttley@dastardlyhq.com - 2024-04-17 08:23 +0000
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-17 11:36 +0200
Re: on Perl Muttley@dastardlyhq.com - 2024-04-17 10:21 +0000
Re: on Perl gazelle@shell.xmission.com (Kenny McCormack) - 2024-04-16 18:09 +0000
Re: on Perl "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2024-04-16 12:05 -0400
Re: on Perl "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2024-04-16 12:25 -0400
Re: on Perl Christian Weisgerber <naddy@mips.inka.de> - 2024-04-16 19:59 +0000
Re: on Perl Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-16 13:36 -0700
Re: on Perl candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-16 16:10 +0000
Re: on Perl Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-17 02:45 +0000
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-17 11:44 +0200
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-17 11:30 +0200
Re: on Perl candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-04-18 15:10 +0000
Re: on Perl David Brown <david.brown@hesbynett.no> - 2024-04-18 21:55 +0200
Re: on Perl Javier <invalid@invalid.invalid> - 2024-04-16 20:47 +0000
Re: on Perl Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-17 03:14 +0000
Re: on Perl Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-04-17 18:04 +0100
Re: on Perl Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-17 23:23 +0000
Re: on Perl Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-04-17 16:59 -0700
Re: on Perl Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-18 01:33 +0000
Re: on Perl Rainer Weikusat <rweikusat@talktalk.net> - 2024-04-18 18:09 +0100
Re: Command Languages Versus Programming Languages David Brown <david.brown@hesbynett.no> - 2024-03-29 13:47 +0100
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-29 20:36 +0000
Re: Command Languages Versus Programming Languages "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-03-30 12:44 +0100
Re: Command Languages Versus Programming Languages Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-30 14:28 -0700
Re: Command Languages Versus Programming Languages "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2024-03-31 22:06 +0200
Re: Command Languages Versus Programming Languages Bozo User <anthk@disroot.org> - 2024-09-30 20:04 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-30 20:59 +0000
Re: Command Languages Versus Programming Languages usuario <anthk@disroot.org> - 2024-10-01 20:41 +0000
Re: Command Languages Versus Programming Languages Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-01 22:22 +0000
Page 13 of 37 — ← Prev page 1 … 11 12 [13] 14 15 … 37 Next page →
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2024-10-09 22:25 +0100 |
| Message-ID | <87a5fdj7f2.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #25687 |
Bozo User <anthk@disroot.org> writes: > On 2024-04-07, Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >> On Sun, 07 Apr 2024 00:01:43 +0000, Javier wrote: >> >>> The downside is the loss of performance because of disk access for >>> trivial things like 'nfiles=$(ls | wc -l)'. >> >> Well, you could save one process creation by writing >> “nfiles=$(echo * | wc -l)” instead. But that would still not be strictly >> correct. >> >>> I suspect disk access times where >>> one of the reasons for the development of perl in the early 90s. >> >> Shells were somewhat less powerful in those days. I would describe the >> genesis of Perl as “awk on steroids”. Its big party trick was regular >> expressions. And I guess combining that with more sophisticated data- >> structuring capabilities. > > Perl is more awk+sed+sh in a single language. Basically the killer > of the Unix philophy in late 90's/early 00's, and for the good. Perl is a high-level programming language with a rich syntax¹, with support for deterministic automatic memory management, functions as first-class objects and message-based OO. It's also a virtual machine for executing threaded code and a(n optimizing) compiler for translating Perl code into the corresponding threaded code. ¹ Has recently gained try/catch for exception handling which is IMNSHO a great improvement over eval + $@.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@DastartdlyHQ.org |
|---|---|
| Date | 2024-10-10 08:38 +0000 |
| Message-ID | <ve83q2$33dfe$1@dont-email.me> |
| In reply to | #25730 |
On Wed, 09 Oct 2024 22:25:05 +0100 Rainer Weikusat <rweikusat@talktalk.net> boring babbled: >Bozo User <anthk@disroot.org> writes: >> On 2024-04-07, Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >>> On Sun, 07 Apr 2024 00:01:43 +0000, Javier wrote: >>> >>>> The downside is the loss of performance because of disk access for >>>> trivial things like 'nfiles=$(ls | wc -l)'. >>> >>> Well, you could save one process creation by writing >>> “nfiles=$(echo * | wc -l)” instead. But that would still not be >strictly >>> correct. >>> >>>> I suspect disk access times where >>>> one of the reasons for the development of perl in the early 90s. >>> >>> Shells were somewhat less powerful in those days. I would describe the >>> genesis of Perl as “awk on steroids”. Its big party trick was regular >>> expressions. And I guess combining that with more sophisticated data- >>> structuring capabilities. >> >> Perl is more awk+sed+sh in a single language. Basically the killer >> of the Unix philophy in late 90's/early 00's, and for the good. > >Perl is a high-level programming language with a rich syntax¹, with >support for deterministic automatic memory management, functions as >first-class objects and message-based OO. It's also a virtual machine >for executing threaded code and a(n optimizing) compiler for translating >Perl code into the corresponding threaded code. Its syntax is also a horrific mess. Larry took the worst parts of C and shell syntax and mashed them together. Its no surprise Perl has been ditched in favour of Python just about everywhere for new scripting projects. And while I hate Pythons meangingful whitespace nonsense, I'd use it in preference to Perl any day.
[toc] | [prev] | [next] | [standalone]
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2024-10-10 16:09 +0100 |
| Message-ID | <87wmighu4i.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #25731 |
Muttley@DastartdlyHQ.org writes: > On Wed, 09 Oct 2024 22:25:05 +0100 > Rainer Weikusat <rweikusat@talktalk.net> boring babbled: >>Bozo User <anthk@disroot.org> writes: >>> On 2024-04-07, Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >>>> On Sun, 07 Apr 2024 00:01:43 +0000, Javier wrote: >>>> >>>>> The downside is the loss of performance because of disk access for >>>>> trivial things like 'nfiles=$(ls | wc -l)'. >>>> >>>> Well, you could save one process creation by writing >>>> “nfiles=$(echo * | wc -l)†instead. But that would still not be >>strictly >>>> correct. >>>> >>>>> I suspect disk access times where >>>>> one of the reasons for the development of perl in the early 90s. >>>> >>>> Shells were somewhat less powerful in those days. I would describe the >>>> genesis of Perl as “awk on steroidsâ€. Its big party trick was regular >>>> expressions. And I guess combining that with more sophisticated data- >>>> structuring capabilities. >>> >>> Perl is more awk+sed+sh in a single language. Basically the killer >>> of the Unix philophy in late 90's/early 00's, and for the good. >> >>Perl is a high-level programming language with a rich syntax¹, with >>support for deterministic automatic memory management, functions as >>first-class objects and message-based OO. It's also a virtual machine >>for executing threaded code and a(n optimizing) compiler for translating >>Perl code into the corresponding threaded code. > > Its syntax is also a horrific mess. Which means precisely what? > Its no surprise Perl has been ditched in favour of Python just about > everywhere for new scripting projects. "I say so and I'm an avid Phython fan?" Not much of a reason. BTW, I didn't mean to start another entirely pointless language war. Just pointing out the referring to a general-purpose programming language as "killer of the UNIX philosophy" makes no sense.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@DastartdlyHQ.org |
|---|---|
| Date | 2024-10-10 15:34 +0000 |
| Message-ID | <ve8s6d$3725r$1@dont-email.me> |
| In reply to | #25732 |
On Thu, 10 Oct 2024 16:09:49 +0100 Rainer Weikusat <rweikusat@talktalk.net> boring babbled: >Muttley@DastartdlyHQ.org writes: >> Its syntax is also a horrific mess. > >Which means precisely what? Far too much pointless punctuation. An interpreter shouldn't need the vartype signified by $ or @ once its defined, it should already know. And then there are semantically meaningful underscores (seriously?) and random hacky keywords such as <STDIN>. I could go on. >> Its no surprise Perl has been ditched in favour of Python just about >> everywhere for new scripting projects. > >"I say so and I'm an avid Phython fan?" > >Not much of a reason. It shows the general consensus of which is an easier language to work with.
[toc] | [prev] | [next] | [standalone]
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2024-10-10 17:55 +0100 |
| Message-ID | <87o73rj3sr.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #25733 |
Muttley@DastartdlyHQ.org ignorantly rambled:
> On Thu, 10 Oct 2024 16:09:49 +0100
> Rainer Weikusat <rweikusat@talktalk.net> boring babbled:
>>Muttley@DastartdlyHQ.org writes:
>>> Its syntax is also a horrific mess.
>>
>>Which means precisely what?
>
> Far too much pointless punctuation. An interpreter shouldn't need the vartype
> signified by $ or @ once its defined, it should already know.
For the purpose of variable declaration, how's the interpeter going to
know the type of a variable without being told about it? Obviously, not
at all.
Perl has three builtin types, scalars, arrays and hashes and
each is denoted by a single-letter prefix which effectively creates
three different variable namespaces, one for each type. That's often
convenient, because the same name can be reused for a variable of a
different type, eg:
my ($data, @data, %data);
$data = rand(128);
@data = ($data, $data + 1);
%data = map { $_, 15 } @data;
it's also convenient to type and easy to read due to being concise.
Outside of declarations, $ and @ really denote access modes/ contexts,
with $ standing for "a thing" and @ for "a number of things", eg
$a[0]
is the first element of the array @a and
@a[-3 .. -1]
is a list composed of the three last elements of @a.
> And then there are semantically meaningful underscores (seriously?)
Similar to the number writing convention in English: 1,600,700, numbers
in Perl can be annotated with _-separators to make them easier to
read. Eg, all of these are identical
1_600_700
16_007_00
1_6_0_0_7_0_0_
But the underscores have no meaning in here.
> and random hacky keywords such as <STDIN>.
<STDIN> isn't a keyword. STDIN is the name of a glob (symbol table
entry) in the symbol table of the package main. It's most prominent use
is (as they name may suggest) to provide access to "the standard input
stream".
<> is an I/O operator. It's operand must be a file handle, ie, either
the name of glob with a file handle associated with it like STDIN or a
scalar variable used to hold a file handle. In scalar context, it reads
and returns the next line read from this file handle. In list context,
it returns all lines in the file.
Eg, this a poor man's implementation of cat:
perl -e 'open($fh, $_) and print <$fh> for @ARGV'
> I could go on.
Please don't enumerate everything else on this planet you also don't
really understand as that's probably going to become a huge list. ;-)
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2024-10-10 19:14 +0000 |
| Message-ID | <20241010120827.867@kylheku.com> |
| In reply to | #25734 |
On 2024-10-10, Rainer Weikusat <rweikusat@talktalk.net> wrote: > Muttley@DastartdlyHQ.org ignorantly rambled: >> On Thu, 10 Oct 2024 16:09:49 +0100 >> Rainer Weikusat <rweikusat@talktalk.net> boring babbled: >>>Muttley@DastartdlyHQ.org writes: >>>> Its syntax is also a horrific mess. >>> >>>Which means precisely what? >> >> Far too much pointless punctuation. An interpreter shouldn't need the vartype >> signified by $ or @ once its defined, it should already know. > > For the purpose of variable declaration, how's the interpeter going to Interpreter? Perl has some kind of compiler in it, right? Interpreters for typed languages are possible. The lexical environment bidnings contain type info, so when the interpreter sees x, it resolves it through the environment not only to a location/value, but to type info. > know the type of a variable without being told about it? Obviously, not > at all. But it's not exactly type, because $x means "scalar variable of any type" whereas @x is an "array of any type". That's quite useless for proper type checking and only causes noise, due to having to be repeated. Actually typed languages don't use sigils. How is that? The type of a name is declared (or else inferred); references to that name don't need to repeat that info. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2024-10-10 21:31 +0100 |
| Message-ID | <87frp3itsk.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #25735 |
Kaz Kylheku <643-408-1753@kylheku.com> writes:
> On 2024-10-10, Rainer Weikusat <rweikusat@talktalk.net> wrote:
>> Muttley@DastartdlyHQ.org ignorantly rambled:
>>> On Thu, 10 Oct 2024 16:09:49 +0100
>>> Rainer Weikusat <rweikusat@talktalk.net> boring babbled:
>>>>Muttley@DastartdlyHQ.org writes:
>>>>> Its syntax is also a horrific mess.
>>>>
>>>>Which means precisely what?
>>>
>>> Far too much pointless punctuation. An interpreter shouldn't need the vartype
>>> signified by $ or @ once its defined, it should already know.
>>
>> For the purpose of variable declaration, how's the interpeter going to
>
> Interpreter? Perl has some kind of compiler in it, right?
The Perl compiler turns Perl source code into a set of (that's a
conjecture of mine) so-called "op trees" whose nodes contain pointers to
built-in functions and pointers to "op subtrees" supplying arguments for
these and the interpeter/ virtual machine then evaluates these op trees
to run the program.
[...]
>> know the type of a variable without being told about it? Obviously, not
>> at all.
>
> But it's not exactly type, because $x means "scalar variable of any
> type" whereas @x is an "array of any type".
$x means 'scalar variable'. There's no furher differentiation of that at
the language level despite there are two kinds of scalar variables at
the implentation level, scalars whose values are "values" of some sort
(ie, strings or numbers) and scalars whose values are references to
something.
@x is an 1-D array of scalars.
> That's quite useless for proper type checking and only causes noise,
> due to having to be repeated.
>
> Actually typed languages don't use sigils. How is that?
>
> The type of a name is declared (or else inferred); references to that
> name don't need to repeat that info.
The Perl type system is based on using different namespaces for
different types which means the type of a variable is part of its
name. This has the advantages that declaration syntax is concise and
that it's possible to have different kinds of variables with the same
name. It's also not really specific to Perl as C uses a similar model
for structures declarations and definitions.
The obvious disadvantage is that every variable name in Perl and every
use of a variable in an expression has and additional meta-information
character associated with it. The actual rules outside of declarations
are also more complicated because of the underlying idea that $ would be
something like a singular article in a spoken language an @ a plural
article. This means that elements of arrays and hashed are referred to
using a $ prefix and not @ or %, eg,
my @a;
$a[0] = 1;
or
my %h;
$h{goatonion} = 'winged cauliflower';
I think that's rather a weird than a great idea but it's internally
consistent and as good (or bad) as any other language ideosyncrasy. It's
certainly less confusing than the : as expression separator in
supposedly punctuation-free Python which tripped me up numerous times
when initially starting to write (some) Python code.
Things only start to get slightly awful when references become
involved. In Perl 4 (reportedly, I've never used that) a reference was a
variable holding the name of another variable, eg
$b = 1;
$a = 'b';
print $$a; # prints 1
Perl 5 added references as typed pointers with reference counting but
retained the symbolic referenc syntax. For the example above, that would
be
$b = 1;
$a = \$b;
print $$a; # also prints 1
Thinks start to become complicated once references to complex objects
are involved. Eg,
@{$$a[0]}
is the array referred to by the first item of the array $a refers to and
${$$a[0]}[0]
which seriously starts to look like a trench fortification with
barbed-wire obstacles is a way to refer to the first element of this
array. The {$$a[0]} is a block returning a reference to an array which
the surrounding $ and [0] then dereference. The { } could contain
arbitrary code returning a reference. But for the simple case of
dereference-chaining, this is not needed as it's implied for adjacent
subscript (for both hashes and arrays) which means the simpler
$$a[0][0]
is equivalent to the other expression.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2024-10-11 00:09 +0100 |
| Message-ID | <ve9mrh$3aiao$2@dont-email.me> |
| In reply to | #25737 |
On 10/10/2024 21:31, Rainer Weikusat wrote:
> Kaz Kylheku <643-408-1753@kylheku.com> writes:
> Thinks start to become complicated once references to complex objects
> are involved. Eg,
>
> @{$$a[0]}
>
> is the array referred to by the first item of the array $a refers to and
>
> ${$$a[0]}[0]
>
> which seriously starts to look like a trench fortification with
> barbed-wire obstacles is a way to refer to the first element of this
> array.
I thought you were defending the language. Now you seem to be agreeing
with how bad this syntax is.
[toc] | [prev] | [next] | [standalone]
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2024-10-11 15:47 +0100 |
| Message-ID | <87jzee3ded.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #25739 |
Bart <bc@freeuk.com> writes:
Kaz Kylheku <643-408-1753@kylheku.com> writes:
> On 2024-10-10, Rainer Weikusat <rweikusat@talktalk.net> wrote:
>> Muttley@DastartdlyHQ.org ignorantly rambled:
>>> On Thu, 10 Oct 2024 16:09:49 +0100
>>> Rainer Weikusat <rweikusat@talktalk.net> boring babbled:
>>>>Muttley@DastartdlyHQ.org writes:
>>>>> Its syntax is also a horrific mess.
>>>>
>>>>Which means precisely what?
>>>
>>> Far too much pointless punctuation. An interpreter shouldn't need the vartype
>>> signified by $ or @ once its defined, it should already know.
>>
>> For the purpose of variable declaration, how's the interpeter going to
>
> Interpreter? Perl has some kind of compiler in it, right?
The Perl compiler turns Perl source code into a set of (that's a
conjecture of mine) so-called "op trees" whose nodes contain pointers to
built-in functions and pointers to "op subtrees" supplying arguments for
these and the interpeter/ virtual machine then evaluates these op trees
to run the program.
[...]
>> know the type of a variable without being told about it? Obviously, not
>> at all.
>
> But it's not exactly type, because $x means "scalar variable of any
> type" whereas @x is an "array of any type".
$x means 'scalar variable'. There's no furher differentiation of that at
the language level despite there are two kinds of scalar variables at
the implentation level, scalars whose values are "values" of some sort
(ie, strings or numbers) and scalars whose values are references to
something.
@x is an 1-D array of scalars.
> That's quite useless for proper type checking and only causes noise,
> due to having to be repeated.
>
> Actually typed languages don't use sigils. How is that?
>
> The type of a name is declared (or else inferred); references to that
> name don't need to repeat that info.
The Perl type system is based on using different namespaces for
different types which means the type of a variable is part of its
name. This has the advantages that declaration syntax is concise and
that it's possible to have different kinds of variables with the same
name. It's also not really specific to Perl as C uses a similar model
for structures declarations and definitions.
The obvious disadvantage is that every variable name in Perl and every
use of a variable in an expression has and additional meta-information
character associated with it. The actual rules outside of declarations
are also more complicated because of the underlying idea that $ would be
something like a singular article in a spoken language an @ a plural
article. This means that elements of arrays and hashed are referred to
using a $ prefix and not @ or %, eg,
my @a;
$a[0] = 1;
or
my %h;
$h{goatonion} = 'winged cauliflower';
I think that's rather a weird than a great idea but it's internally
consistent and as good (or bad) as any other language ideosyncrasy. It's
certainly less confusing than the : as expression separator in
supposedly punctuation-free Python which tripped me up numerous times
when initially starting to write (some) Python code.
Things only start to get slightly awful when references become
involved. In Perl 4 (reportedly, I've never used that) a reference was a
variable holding the name of another variable, eg
$b = 1;
$a = 'b';
print $$a; # prints 1
Perl 5 added references as typed pointers with reference counting but
retained the symbolic referenc syntax. For the example above, that would
be
$b = 1;
$a = \$b;
print $$a; # also prints 1
Thinks start to become complicated once references to complex objects
are involved. Eg,
@{$$a[0]}
is the array referred to by the first item of the array $a refers to and
${$$a[0]}[0]
which seriously starts to look like a trench fortification with
barbed-wire obstacles is a way to refer to the first element of this
array. The {$$a[0]} is a block returning a reference to an array which
the surrounding $ and [0] then dereference. The { } could contain
arbitrary code returning a reference. But for the simple case of
dereference-chaining, this is not needed as it's implied for adjacent
subscript (for both hashes and arrays) which means the simpler
$$a[0][0]
is equivalent to the other expression.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@DastartdlyHQ.org |
|---|---|
| Date | 2024-10-11 15:15 +0000 |
| Message-ID | <vebffc$3n6jv$1@dont-email.me> |
| In reply to | #25742 |
On Fri, 11 Oct 2024 15:47:06 +0100 Rainer Weikusat <rweikusat@talktalk.net> boring babbled: >Bart <bc@freeuk.com> writes: >> Interpreter? Perl has some kind of compiler in it, right? > >The Perl compiler turns Perl source code into a set of (that's a Does it produce a standalone binary as output? No, so its an intepreter not a compiler. However unlike the python interpreter its non interactive making it an even less attractive option these days.
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2024-10-11 15:45 +0000 |
| Message-ID | <vebh5t$mnh$1@reader1.panix.com> |
| In reply to | #25744 |
In article <vebffc$3n6jv$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >On Fri, 11 Oct 2024 15:47:06 +0100 >Rainer Weikusat <rweikusat@talktalk.net> boring babbled: >>Bart <bc@freeuk.com> writes: >>> Interpreter? Perl has some kind of compiler in it, right? >> >>The Perl compiler turns Perl source code into a set of (that's a > >Does it produce a standalone binary as output? No, so its an intepreter >not a compiler. However unlike the python interpreter its non interactive >making it an even less attractive option these days. That's a bad distinction. There have been "Load and Go" compilers in the past that have compiled and linked a program directly into memory and executed it immediately after compilation. As I recall, the Waterloo FORTRAN compilers on the IBM mainframe did, or could do, more or less this. Saving to some sort of object image is not a necessary function of a compiler. - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@DastartdlyHQ.org |
|---|---|
| Date | 2024-10-11 15:59 +0000 |
| Message-ID | <vebi0j$3nhvq$1@dont-email.me> |
| In reply to | #25745 |
On Fri, 11 Oct 2024 15:45:01 -0000 (UTC) cross@spitfire.i.gajendra.net (Dan Cross) boring babbled: >In article <vebffc$3n6jv$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >>On Fri, 11 Oct 2024 15:47:06 +0100 >>Rainer Weikusat <rweikusat@talktalk.net> boring babbled: >>>Bart <bc@freeuk.com> writes: >>>> Interpreter? Perl has some kind of compiler in it, right? >>> >>>The Perl compiler turns Perl source code into a set of (that's a >> >>Does it produce a standalone binary as output? No, so its an intepreter >>not a compiler. However unlike the python interpreter its non interactive >>making it an even less attractive option these days. > >That's a bad distinction. There have been "Load and Go" >compilers in the past that have compiled and linked a program >directly into memory and executed it immediately after >compilation. As I recall, the Waterloo FORTRAN compilers on the >IBM mainframe did, or could do, more or less this. Irrelevant. Lot of interpreters do partial compilation and the JVM does it on the fly. A proper compiler writes a standalone binary file to disk. >Saving to some sort of object image is not a necessary function >of a compiler. Yes it is.
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2024-10-11 16:28 +0000 |
| Message-ID | <vebjmj$5dc$1@reader1.panix.com> |
| In reply to | #25746 |
In article <vebi0j$3nhvq$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >On Fri, 11 Oct 2024 15:45:01 -0000 (UTC) >cross@spitfire.i.gajendra.net (Dan Cross) boring babbled: >>In article <vebffc$3n6jv$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >>>On Fri, 11 Oct 2024 15:47:06 +0100 >>>Rainer Weikusat <rweikusat@talktalk.net> boring babbled: >>>>Bart <bc@freeuk.com> writes: >>>>> Interpreter? Perl has some kind of compiler in it, right? >>>> >>>>The Perl compiler turns Perl source code into a set of (that's a >>> >>>Does it produce a standalone binary as output? No, so its an intepreter >>>not a compiler. However unlike the python interpreter its non interactive >>>making it an even less attractive option these days. >> >>That's a bad distinction. There have been "Load and Go" >>compilers in the past that have compiled and linked a program >>directly into memory and executed it immediately after >>compilation. As I recall, the Waterloo FORTRAN compilers on the >>IBM mainframe did, or could do, more or less this. > >Irrelevant. Lot of interpreters do partial compilation and the JVM does it >on the fly. A proper compiler writes a standalone binary file to disk. Not generally, no. Most compilers these days generate object code and then, as a separate step, a linker is invoked to combine object files and library archives into an executable binary. By the way, when many people talk about a "standalone" binary, they are referring to something directly executable on hardware, without the benefit of an operating system. The Unix kernel is an example of such a "standalone binary." Most executable binaries are not standalone. >>Saving to some sort of object image is not a necessary function >>of a compiler. > >Yes it is. So you say, but that's not the commonly accepted definition. Sorry. - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@DastartdlyHQ.org |
|---|---|
| Date | 2024-10-12 08:39 +0000 |
| Message-ID | <vedcjc$3mqn$1@dont-email.me> |
| In reply to | #25747 |
On Fri, 11 Oct 2024 16:28:03 -0000 (UTC) cross@spitfire.i.gajendra.net (Dan Cross) boring babbled: >In article <vebi0j$3nhvq$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >>Irrelevant. Lot of interpreters do partial compilation and the JVM does it >>on the fly. A proper compiler writes a standalone binary file to disk. > >Not generally, no. Most compilers these days generate object >code and then, as a separate step, a linker is invoked to >combine object files and library archives into an executable >binary. Ok, the compiler toolchain then. Most people invoke it using a single command, the rest is behind the scenes. >By the way, when many people talk about a "standalone" binary, >they are referring to something directly executable on hardware, For many read a tiny minority. >without the benefit of an operating system. The Unix kernel is >an example of such a "standalone binary." If you're going to nitpick then I'm afraid you're wrong. Almost all operating systems require some kind of bootloader and/or BIOS combination to start them up. You can't just point the CPU at the first byte of the binary and off it goes particularly in the case of Linux where the kernel requires decompressing first. >Most executable binaries are not standalone. Standalone as you are well aware in the sense of doesn't require an interpreter or VM to run on the OS and contains CPU machine code. >>>Saving to some sort of object image is not a necessary function >>>of a compiler. >> >>Yes it is. > >So you say, but that's not the commonly accepted definition. >Sorry. Where do you get this commonly accepted definition from?
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2024-10-12 13:53 +0000 |
| Message-ID | <vedv1k$idp$1@reader1.panix.com> |
| In reply to | #25764 |
In article <vedcjc$3mqn$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >On Fri, 11 Oct 2024 16:28:03 -0000 (UTC) >cross@spitfire.i.gajendra.net (Dan Cross) boring babbled: >>In article <vebi0j$3nhvq$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >>>Irrelevant. Lot of interpreters do partial compilation and the JVM does it >>>on the fly. A proper compiler writes a standalone binary file to disk. >> >>Not generally, no. Most compilers these days generate object >>code and then, as a separate step, a linker is invoked to >>combine object files and library archives into an executable >>binary. > >Ok, the compiler toolchain then. Most people invoke it using a single command, >the rest is behind the scenes. > >>By the way, when many people talk about a "standalone" binary, >>they are referring to something directly executable on hardware, > >For many read a tiny minority. > >>without the benefit of an operating system. The Unix kernel is >>an example of such a "standalone binary." > >If you're going to nitpick then I'm afraid you're wrong. Almost all operating >systems require some kind of bootloader and/or BIOS combination to start them >up. You can't just point the CPU at the first byte of the binary and off it >goes particularly in the case of Linux where the kernel requires decompressing >first. Again, not generally, no. Consider an embedded system where the program to be executed on, say, a microcontroller is itself statically linked at an absolute address and burned into a ROM, with the program's entry point at the CPU's reset address. I suppose that's not "standalone" if you count a ROM burner as part of "loading" it. Also, I mentioned Unix, not Linux. The two are different. The first version of the Unix kernel started at a fixed location on the PDP-7, without a separate loading step (Ken Thompson did that manually). Of course, this all gets more complex when we start talking about modern systems with loading kernel modules and the like. >>Most executable binaries are not standalone. > >Standalone as you are well aware in the sense of doesn't require an interpreter >or VM to run on the OS and contains CPU machine code. So what about a binary that is dynamically linked with a shared object? That requires a runtime interpreter nee linker to bind its constituent parts together before it's executable. And what if it makes a system call? Then it's no longer "standalone", as it necessarily relies on the operating system to perform part of its function. But that's really neither here nor there; I think you are conflating object code with text containing instructions meant for direct execution on a CPU with something like a P-code; the distinction is kind of silly when you consider that we live in a world with CPU simulators that let you boot entire systems for architecture A in a program running on architecture B, usually in userspace. Why do you think that a compiler that generates bytecode for some virtual machine is any different from a compiler that generates object code for some CPU? You don't seem to be able to recognize that the compilation step is separate from execution, and that the same techniques for compiler development apply to both hardware and virtual targets. >>>>Saving to some sort of object image is not a necessary function >>>>of a compiler. >>> >>>Yes it is. >> >>So you say, but that's not the commonly accepted definition. >>Sorry. > >Where do you get this commonly accepted definition from? *shrug* Tanenbaum; Silberschatz; Kaashoek; Roscoe; etc. Where did you get your definition? - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@dastardlyhq.com |
|---|---|
| Date | 2024-10-12 14:50 +0000 |
| Message-ID | <vee2b1$6vup$1@dont-email.me> |
| In reply to | #25770 |
On Sat, 12 Oct 2024 13:53:56 -0000 (UTC) cross@spitfire.i.gajendra.net (Dan Cross) gabbled: >In article <vedcjc$3mqn$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >>up. You can't just point the CPU at the first byte of the binary and off it >>goes particularly in the case of Linux where the kernel requires decompressing > >>first. > >Again, not generally, no. Consider an embedded system where the >program to be executed on, say, a microcontroller is itself >statically linked at an absolute address and burned into a ROM, Unlikely to be running *nix in that case. >with the program's entry point at the CPU's reset address. I >suppose that's not "standalone" if you count a ROM burner as >part of "loading" it. Now you're just being silly. >Also, I mentioned Unix, not Linux. The two are different. The Are they? Thats debatable these days. I'd say Linux is a lot closer to the philosphy of BSD and SYS-V than MacOS which is a certified unix. >>Standalone as you are well aware in the sense of doesn't require an >interpreter >>or VM to run on the OS and contains CPU machine code. > >So what about a binary that is dynamically linked with a shared >object? That requires a runtime interpreter nee linker to bind >its constituent parts together before it's executable. And what >if it makes a system call? Then it's no longer "standalone", as >it necessarily relies on the operating system to perform part of >its function. Standalone in the sense that the opcodes in the binary don't need to be transformed into something else before being loaded by the CPU. >usually in userspace. Why do you think that a compiler that >generates bytecode for some virtual machine is any different >from a compiler that generates object code for some CPU? I'd say its a grey area because it isn't full compilation is it, the p-code still requires an interpreter before it'll run. >You don't seem to be able to recognize that the compilation step Compiling is not the same as converting. Is a javascript to C converter a compiler? By your definition it is. >>Where do you get this commonly accepted definition from? > >*shrug* Tanenbaum; Silberschatz; Kaashoek; Roscoe; etc. Where >did you get your definition? Only heard of one of them so mostly irrelevant. Mine come from the name of tools that compile code to a runnable binary.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2024-10-12 15:32 +0000 |
| Message-ID | <gEwOO.82300$S9Vb.81024@fx45.iad> |
| In reply to | #25771 |
Muttley@dastardlyhq.com writes: >On Sat, 12 Oct 2024 13:53:56 -0000 (UTC) >cross@spitfire.i.gajendra.net (Dan Cross) gabbled: >>In article <vedcjc$3mqn$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >>>up. You can't just point the CPU at the first byte of the binary and off it >>>goes particularly in the case of Linux where the kernel requires decompressing >> >>>first. >> >>Again, not generally, no. Consider an embedded system where the >>program to be executed on, say, a microcontroller is itself >>statically linked at an absolute address and burned into a ROM, > >Unlikely to be running *nix in that case. Some do, some don't. Many run zephyr, others various commercial embedded RTOS. In any case, they're binaries and if properly created, one simply points the cpu to the first byte of the binary (or more likely some standard PC value that the processor starts fetching from when it leaves reset, e.g. the VTOR on Cortex-m7 cores) and off it goes. >>So what about a binary that is dynamically linked with a shared >>object? That requires a runtime interpreter nee linker to bind >>its constituent parts together before it's executable. And what >>if it makes a system call? Then it's no longer "standalone", as >>it necessarily relies on the operating system to perform part of >>its function. > >Standalone in the sense that the opcodes in the binary don't need to be >transformed into something else before being loaded by the CPU. That's a rather unique definition of 'standalone'.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@dastardlyhq.com |
|---|---|
| Date | 2024-10-12 15:51 +0000 |
| Message-ID | <vee5te$7h5p$1@dont-email.me> |
| In reply to | #25772 |
On Sat, 12 Oct 2024 15:32:28 GMT scott@slp53.sl.home (Scott Lurndal) gabbled: >Muttley@dastardlyhq.com writes: >>Standalone in the sense that the opcodes in the binary don't need to be >>transformed into something else before being loaded by the CPU. > >That's a rather unique definition of 'standalone'. Is it? As opposed to something that requires a seperate program to run any of it. That java p-code isn't going to do much without a jvm to translate it into x86 or ARM etc whereas a compiled binary will - after required libraries are loaded with it - just run directly on the CPU.
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2024-10-12 16:36 +0000 |
| Message-ID | <vee8ia$hkq$1@reader1.panix.com> |
| In reply to | #25771 |
In article <vee2b1$6vup$1@dont-email.me>, <Muttley@dastardlyhq.com> wrote: >On Sat, 12 Oct 2024 13:53:56 -0000 (UTC) >cross@spitfire.i.gajendra.net (Dan Cross) gabbled: >>In article <vedcjc$3mqn$1@dont-email.me>, <Muttley@DastartdlyHQ.org> wrote: >>>up. You can't just point the CPU at the first byte of the binary and off it >>>goes particularly in the case of Linux where the kernel requires decompressing >> >>>first. >> >>Again, not generally, no. Consider an embedded system where the >>program to be executed on, say, a microcontroller is itself >>statically linked at an absolute address and burned into a ROM, > >Unlikely to be running *nix in that case. We're discussing the concept of a "standalone binary"; you seem to think that means a binary image emitted by a linker and meant to run under a hosted environment, like an operating system. It does not. >>with the program's entry point at the CPU's reset address. I >>suppose that's not "standalone" if you count a ROM burner as >>part of "loading" it. > >Now you're just being silly. *shrug* Not my problem if you haven't dealt with many embedded systems. >>Also, I mentioned Unix, not Linux. The two are different. The > >Are they? Thats debatable these days. I'd say Linux is a lot closer to >the philosphy of BSD and SYS-V than MacOS which is a certified unix. Yes, they are. >>>Standalone as you are well aware in the sense of doesn't require an >>interpreter >>>or VM to run on the OS and contains CPU machine code. >> >>So what about a binary that is dynamically linked with a shared >>object? That requires a runtime interpreter nee linker to bind >>its constituent parts together before it's executable. And what >>if it makes a system call? Then it's no longer "standalone", as >>it necessarily relies on the operating system to perform part of >>its function. > >Standalone in the sense that the opcodes in the binary don't need to be >transformed into something else before being loaded by the CPU. Yeah, no, that's not what anybody serious means when they say that. >>usually in userspace. Why do you think that a compiler that >>generates bytecode for some virtual machine is any different >>from a compiler that generates object code for some CPU? > >I'd say its a grey area because it isn't full compilation is it, the p-code >still requires an interpreter before it'll run. Nope. >>You don't seem to be able to recognize that the compilation step > >Compiling is not the same as converting. Is a javascript to C converter a >compiler? By your definition it is. Yes, of course it is. So is the terminfo compiler, and any number of other similar things. The first C++ compiler, cfront emitted C code, not object code. Was it not a compiler? >>>Where do you get this commonly accepted definition from? >> >>*shrug* Tanenbaum; Silberschatz; Kaashoek; Roscoe; etc. Where >>did you get your definition? > >Only heard of one of them so mostly irrelevant. Mine come from the name of >tools that compile code to a runnable binary. It's very odd that you seek to speak from a position of authority when you don't even know who most of the major people in the field are. - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@DastartdlyHQ.org |
|---|---|
| Date | 2024-10-13 08:18 +0000 |
| Message-ID | <vefvo0$k1mm$1@dont-email.me> |
| In reply to | #25776 |
On Sat, 12 Oct 2024 16:36:26 -0000 (UTC) cross@spitfire.i.gajendra.net (Dan Cross) boring babbled: >In article <vee2b1$6vup$1@dont-email.me>, <Muttley@dastardlyhq.com> wrote: >>Unlikely to be running *nix in that case. > >We're discussing the concept of a "standalone binary"; you seem >to think that means a binary image emitted by a linker and meant >to run under a hosted environment, like an operating system. It >does not. It can mean either. Essentially its a binary that contains directly runnable CPU machine code. I'm not sure why you're having such a conceptual struggle understanding this simple concept. >>Now you're just being silly. > >*shrug* Not my problem if you haven't dealt with many embedded >systems. I could bore you with the number I've actually "dealt with" including military hardware but whats the point. You've probably programmed the occasional PIC or arduino and think you're an expert. >>Are they? Thats debatable these days. I'd say Linux is a lot closer to >>the philosphy of BSD and SYS-V than MacOS which is a certified unix. > >Yes, they are. I disagree. Modern linux reminds me a lot of SunOS and HP-UX from back in the day. Not something that can be said for MacOS with its role-our-own Apple specific way of doing pretty much everything. >>Standalone in the sense that the opcodes in the binary don't need to be >>transformed into something else before being loaded by the CPU. > >Yeah, no, that's not what anybody serious means when they say >that. Anybody serious presumably meaning you. >>I'd say its a grey area because it isn't full compilation is it, the p-code >>still requires an interpreter before it'll run. > >Nope. Really? So java bytecode will run direct on x86 or ARM will it? Please give some links to this astounding discovery you've made. >>Compiling is not the same as converting. Is a javascript to C converter a >>compiler? By your definition it is. > >Yes, of course it is. So is the terminfo compiler, and any So in your mind google translate is a "compiler" for spoken languages is it? >number of other similar things. The first C++ compiler, cfront >emitted C code, not object code. Was it not a compiler? No, it was a pre-compiler. Just like Oracles PRO*C/C++. >>Only heard of one of them so mostly irrelevant. Mine come from the name of >>tools that compile code to a runnable binary. > >It's very odd that you seek to speak from a position of >authority when you don't even know who most of the major people >in the field are. I know the important ones. You've dug out some obscure names from google that probably only a few CS courses even mention never mind study the work of.
[toc] | [prev] | [next] | [standalone]
Page 13 of 37 — ← Prev page 1 … 11 12 [13] 14 15 … 37 Next page →
Back to top | Article view | comp.unix.shell
csiph-web