Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #401667 > unrolled thread
| Started by | fir <profesor.fir@gmail.com> |
|---|---|
| First post | 2026-09-06 15:45 +0200 |
| Last post | 2026-10-05 04:32 +0200 |
| Articles | 20 on this page of 496 — 24 participants |
Back to article view | Back to comp.lang.c
Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-06 15:45 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-06 15:52 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-06 16:52 +0100
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-06 21:41 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-07 09:37 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-07 11:35 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-07 13:15 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-07 13:55 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-07 15:24 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-07 15:33 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-07 16:34 +0100
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-08 00:50 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-08 00:35 +0100
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-07 17:43 -0600
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-07 16:52 -0700
Re: Official list of top C annoyances Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-09 15:24 +0800
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 10:18 +0200
Re: Official list of top C annoyances Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-09 20:16 +0800
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 14:31 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 14:37 +0200
Re: Official list of top C annoyances Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-09 21:37 +0800
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-18 09:38 +0200
Re: Official list of top C annoyances Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-18 17:42 +0800
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-08 03:11 +0200
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-08 16:40 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-08 20:08 +0100
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 09:35 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 10:18 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 12:32 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 14:30 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 15:09 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 16:58 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 18:34 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-09 18:37 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 20:12 +0100
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 22:11 +0200
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-09 21:15 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 23:37 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 21:39 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 21:39 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-10 09:07 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-09 14:41 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 23:31 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-09 15:10 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-08 09:25 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 09:59 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 10:35 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 11:35 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 14:43 +0200
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-10 14:08 -0700
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-10 14:14 -0700
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-11 09:16 +0200
Re: Official list of top C annoyances Kaz Kylheku <046-301-5902@kylheku.com> - 2026-09-14 19:14 +0000
Re: Official list of top C annoyances Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-09-18 08:29 -0700
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-09 02:45 -0700
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 15:07 +0200
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-09 07:14 -0600
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 15:31 +0200
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-09 07:41 -0600
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 15:58 +0200
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-09 08:05 -0600
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 16:13 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-09 16:29 -0700
Re: Official list of top C annoyances "Johann \"Myrkraverk\" Oskarsson" <johann@myrkraverk.invalid> - 2026-09-18 10:23 +0800
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 16:10 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 16:19 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 17:02 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 15:11 +0100
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-09 08:25 -0600
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 15:53 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 17:42 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 17:53 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 18:03 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 18:19 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 18:49 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 19:16 +0200
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-09 15:48 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 18:38 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-10 09:11 +0200
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-09 15:04 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 17:12 +0200
Re: Official list of top C annoyances "Johann \"Myrkraverk\" Oskarsson" <johann@myrkraverk.invalid> - 2026-09-09 23:59 +0800
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-09 15:30 -0700
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-10 06:50 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-09 15:13 -0700
Re: Official list of top C annoyances Richard Harnden <richard.nospam@gmail.invalid> - 2026-09-09 15:16 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-09 15:43 -0700
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-10 07:16 +0200
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-08 00:02 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-08 12:47 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-09 01:59 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 10:26 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 19:12 +0100
Re: Official list of top C annoyances tTh <tth@none.invalid> - 2026-09-09 21:01 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 21:45 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 21:18 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-10 09:32 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 23:26 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-09 23:30 +0100
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-10 08:45 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-10 13:09 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 14:37 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 15:11 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 15:16 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 15:28 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-10 14:33 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 15:51 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 16:03 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-10 15:27 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 16:45 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 16:59 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-10 16:57 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 18:18 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 01:04 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 16:47 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 16:54 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 17:06 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 17:15 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-10 18:10 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 18:21 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-10 18:45 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 18:56 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 19:01 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 19:20 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 20:19 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 20:25 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 19:17 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-11 09:21 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 12:46 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 14:13 +0200
Re: Official list of top C annoyances Richard Harnden <richard.nospam@gmail.invalid> - 2026-09-11 13:41 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 14:55 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 15:01 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 15:04 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 15:08 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 15:13 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-11 15:17 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 21:02 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 21:59 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 16:41 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-10 09:48 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-11 00:06 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-10 23:48 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-10 15:52 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-11 00:48 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-10 17:11 -0700
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-12 08:01 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 08:20 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 09:09 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 12:35 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 12:40 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-12 11:55 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 14:37 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 14:49 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 15:00 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-12 14:24 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 15:44 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 15:53 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 16:05 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 16:16 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 17:20 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-12 17:08 +0100
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-12 10:53 -0600
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 19:23 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-12 18:58 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 20:35 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 20:46 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 20:49 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-12 22:16 +0100
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-12 15:40 -0600
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 10:15 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 10:27 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 10:39 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-13 10:30 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 11:47 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 11:53 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-13 11:26 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 12:37 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 12:47 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 12:55 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 13:11 +0200
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-13 05:29 -0600
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 13:43 +0200
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-13 14:00 -0700
Re: Official list of top C annoyances Ike Naar <ike@sdf.org> - 2026-09-13 10:53 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-13 13:46 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 15:21 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-13 15:31 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 16:34 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 16:58 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-13 18:01 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 21:14 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 17:17 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 17:23 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 17:27 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-13 17:06 -0700
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-14 15:01 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-14 18:11 +0200
Re: Official list of top C annoyances tTh <tth@none.invalid> - 2026-09-14 20:21 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-14 22:54 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-14 23:56 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-15 09:07 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-15 09:41 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-15 10:22 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-15 11:51 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-15 12:53 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-18 09:10 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-18 11:37 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-19 09:03 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-19 13:01 +0200
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-05 01:57 +0000
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-14 18:54 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-14 22:55 +0200
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-14 21:03 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-15 00:33 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-13 10:50 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-13 12:32 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 20:15 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 19:34 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 19:39 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-12 15:23 +0200
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-12 07:45 -0600
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-11 00:37 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-13 18:55 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-14 01:44 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-14 07:41 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-14 14:01 +0100
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-14 14:09 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-15 02:42 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-14 23:41 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-15 01:48 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-15 07:39 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-15 11:28 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-15 14:54 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-15 21:56 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-15 21:34 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 00:36 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-16 02:21 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-16 09:08 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 11:21 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-16 13:47 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 15:20 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-16 17:53 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 00:36 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-16 16:59 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 01:49 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-16 19:43 -0700
Re: Official list of top C annoyances tTh <tth@none.invalid> - 2026-09-17 09:24 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 11:29 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-17 15:06 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 02:04 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-17 18:19 -0700
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-18 11:27 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 11:21 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-18 13:17 +0200
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-18 15:44 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-19 09:16 +0200
Re: Official list of top C annoyances cross@spitfire.i.gajendra.net (Dan Cross) - 2026-09-18 12:55 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-18 17:53 +0300
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-18 15:47 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-19 21:22 +0300
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-20 15:58 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-21 21:06 +0300
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-22 15:04 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-22 21:07 +0300
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-18 15:41 +0000
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 11:34 -0700
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-17 12:52 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 13:15 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-17 15:16 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 15:25 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-17 17:05 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 16:46 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-17 20:22 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 20:19 +0100
Re: Official list of top C annoyances tTh <tth@none.invalid> - 2026-09-17 21:55 +0200
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-17 23:47 +0000
Re: Official list of top C annoyances tTh <tth@none.invalid> - 2026-09-17 21:31 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 20:54 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-17 15:44 -0700
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-17 23:48 +0000
Re: Official list of top C annoyances "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-09-18 00:04 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 01:34 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-17 17:50 -0700
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-18 17:45 +0300
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-18 15:28 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-18 18:34 +0300
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-18 18:08 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 11:26 -0700
Re: Official list of top C annoyances gazelle@shell.xmission.com (Kenny McCormack) - 2026-09-18 20:39 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-19 13:10 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-19 13:20 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-19 17:30 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-19 09:38 +0200
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-19 21:00 +0300
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-20 10:17 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-20 11:29 +0100
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-20 12:52 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-10-06 01:06 +0000
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-20 15:58 -0700
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-20 15:55 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-21 20:41 +0300
Re: Official list of top C annoyances Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-22 01:53 +0800
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-22 11:28 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-22 11:34 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-22 15:00 +0000
Re: Official list of top C annoyances Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-09-22 14:22 +0000
Re: Official list of top C annoyances Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-09-22 15:04 +0000
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-22 16:38 +0000
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-30 02:28 +0000
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-10-06 01:29 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-19 22:01 +0300
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-18 20:28 +0000
Re: Official list of top C annoyances "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-09-18 05:42 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-18 08:08 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 10:23 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-18 15:24 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 16:31 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 11:29 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 20:14 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 12:42 -0700
Re: Official list of top C annoyances Jim Jackson <jj@franjam.org.uk> - 2026-09-19 13:39 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-19 16:24 +0100
Re: Official list of top C annoyances "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-09-19 00:19 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-19 02:06 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 20:20 -0700
Re: Official list of top C annoyances "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-09-19 03:26 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-19 09:56 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-19 11:08 +0100
Re: Official list of top C annoyances tTh <tth@none.invalid> - 2026-09-19 13:25 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-19 10:45 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-19 15:09 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-19 16:17 +0100
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-19 09:45 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-18 13:11 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 14:03 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-18 17:24 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 11:06 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 20:07 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 12:26 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 22:57 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-19 17:27 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-19 20:09 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-20 12:31 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-20 12:42 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-20 15:08 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-20 14:22 +0100
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-20 14:54 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-20 23:24 +0200
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-21 15:06 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-21 16:36 +0100
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-21 17:45 +0200
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-21 20:54 +0300
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-22 15:02 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-22 21:02 +0300
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-20 15:58 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-20 15:19 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-20 23:49 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-20 16:17 -0700
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-20 15:49 +0000
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-20 15:18 -0700
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-20 15:41 +0000
Re: Official list of top C annoyances tTh <tth@none.invalid> - 2026-09-17 21:53 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 21:05 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-17 14:38 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-17 17:15 +0200
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-17 16:33 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-17 20:26 +0200
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-17 13:26 -0700
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-17 13:25 -0700
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-17 12:36 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 13:03 +0100
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-17 14:51 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-17 14:32 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-17 15:17 -0700
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-17 15:24 -0700
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-18 09:06 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 02:08 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 11:01 +0100
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-18 03:05 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-18 11:13 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-16 17:33 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 19:19 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-16 18:34 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 20:21 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-16 13:16 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 15:26 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-16 15:58 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 19:13 +0100
Re: Official list of top C annoyances scott@slp53.sl.home (Scott Lurndal) - 2026-09-16 18:30 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 20:30 +0100
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-16 21:16 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-17 02:56 +0000
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-30 02:32 +0000
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-29 19:58 -0700
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-05 02:15 +0000
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-29 03:22 +0000
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-14 09:49 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-14 11:27 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-14 16:03 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-14 16:15 +0200
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-22 23:27 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-23 01:01 +0100
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-23 23:38 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-24 02:00 +0100
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-24 02:41 +0000
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-23 20:23 -0700
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-24 11:27 +0100
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-24 23:54 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-25 01:23 +0100
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-25 03:47 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-25 11:38 +0100
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-26 02:49 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-26 11:44 +0100
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-26 14:03 +0100
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-28 00:05 +0000
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-29 00:56 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-29 14:27 +0100
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-30 02:02 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-30 11:18 +0100
Re: Official list of top C annoyances cross@spitfire.i.gajendra.net (Dan Cross) - 2026-09-30 13:37 +0000
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-30 17:17 +0300
Re: Official list of top C annoyances cross@spitfire.i.gajendra.net (Dan Cross) - 2026-09-30 14:39 +0000
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-30 22:39 +0000
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-01 15:23 -0700
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-02 02:38 +0000
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-10-02 09:17 +0200
Re: Official list of top C annoyances Michael S <already5chosen@yahoo.com> - 2026-09-25 12:17 +0300
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-25 11:31 +0100
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-26 02:34 +0000
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-24 08:50 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-24 11:31 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-24 11:29 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-25 21:09 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-26 11:59 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-29 04:06 +0000
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-29 04:47 +0000
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-29 23:49 +0100
Re: Official list of top C annoyances antispam@fricas.org (Waldek Hebisch) - 2026-09-30 12:19 +0000
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 10:13 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-09 10:38 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 11:40 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 12:05 +0200
Re: Official list of top C annoyances Richard Harnden <richard.nospam@gmail.invalid> - 2026-09-09 15:23 +0100
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 23:07 +0200
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-09 15:52 -0700
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 01:00 +0200
Re: Official list of top C annoyances "Johann \"Myrkraverk\" Oskarsson" <johann@myrkraverk.invalid> - 2026-09-18 10:17 +0800
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-18 09:29 +0200
Re: Official list of top C annoyances Jim Jackson <jj@franjam.org.uk> - 2026-09-19 13:46 +0000
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-25 09:15 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-10 06:16 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 14:38 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 18:35 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-10 18:36 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-10 10:11 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-11 00:48 +0200
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-29 03:18 +0000
Re: Official list of top C annoyances Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-09-18 12:58 -0700
Re: Official list of top C annoyances Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-22 23:21 +0000
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-08 12:47 -0700
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-07 15:20 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-07 09:53 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-07 23:59 +0200
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-07 16:04 -0600
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-07 04:06 -0700
Re: Official list of top C annoyances Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-07 20:05 +0800
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-07 15:32 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-08 12:59 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-08 13:09 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-08 14:15 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-08 14:35 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-08 14:49 +0200
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-08 16:05 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-08 16:18 +0200
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-08 09:45 -0600
Re: Official list of top C annoyances David Brown <david.brown@hesbynett.no> - 2026-09-08 20:41 +0200
Re: Official list of top C annoyances "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-08 12:39 -0700
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-08 15:55 -0700
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-08 18:02 -0600
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-08 17:39 -0700
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-08 18:47 -0600
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-08 18:19 -0700
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-08 19:24 -0600
Re: Official list of top C annoyances Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-08 19:26 -0700
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-09 03:25 +0200
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 09:13 +0200
Re: Official list of top C annoyances Lane W <cactus_DAC@yahoo.com> - 2026-09-09 07:38 -0600
Re: Official list of top C annoyances "Johann \"Myrkraverk\" Oskarsson" <johann@myrkraverk.invalid> - 2026-09-09 22:16 +0800
Re: Official list of top C annoyances Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 09:02 +0200
Re: Official list of top C annoyances Jan van den Broek <balglaas@dds.nl> - 2026-09-09 12:50 +0000
And then we reached C# (was Re: Official list of top C annoyances) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 08:51 +0200
Re: Official list of top C annoyances bart <bc@freeuk.com> - 2026-09-08 14:54 +0100
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-08 16:10 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-09-25 14:22 +0200
Re: Official list of top C annoyances fir <profesor.fir@gmail.com> - 2026-10-05 04:32 +0200
Page 16 of 25 — ← Prev page 1 … 14 15 [16] 17 18 … 25 Next page →
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2026-09-20 15:55 +0000 |
| Message-ID | <GlTrS.40143$iUXd.10884@fx04.iad> |
| In reply to | #402284 |
Michael S <already5chosen@yahoo.com> writes: >On Fri, 18 Sep 2026 18:08:38 +0200 >David Brown <david.brown@hesbynett.no> wrote: >> """ >> as is primarily intended to assemble the output of the GNU C compiler >> "gcc" for use by the linker "ld". Nevertheless, we've tried to make >> as assemble correctly everything that other assemblers for the same >> machine would assemble. Any exceptions are documented explicitly. >> This doesn't mean as always uses the same syntax as another assembler >> for the same architecture; for example, we know of several >> incompatible versions of 680x0 assembly language syntax. >> > >I don't know when this paragraph was written. >Today's gnu as is pretty reasonable tool for assembler develpment. >Decent macro capabilities etc... Likely, not on par with >macro-assemblers of IBM mainframes or of VAX/VMS, but rather similar in >capabilities to Microsoft's Masm or with nasm. >Certainly it is far more complete tool than what would be neeaded to >process gcc output into objects. While true, David's point stands. By far and away, usage of as(1) is most common in a compiler pipeline. It is extremly rare (other than for operating system processor initialization code on Intel moving from real mode to long mode and for processor exception and interrupt handling) for anyone to write direct assembler code in modern software development environments.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2026-09-21 20:41 +0300 |
| Message-ID | <20260921204118.00005c30@yahoo.com> |
| In reply to | #402307 |
On Sun, 20 Sep 2026 15:55:18 GMT scott@slp53.sl.home (Scott Lurndal) wrote: > Michael S <already5chosen@yahoo.com> writes: > >On Fri, 18 Sep 2026 18:08:38 +0200 > >David Brown <david.brown@hesbynett.no> wrote: > > >> """ > >> as is primarily intended to assemble the output of the GNU C > >> compiler "gcc" for use by the linker "ld". Nevertheless, we've > >> tried to make as assemble correctly everything that other > >> assemblers for the same machine would assemble. Any exceptions > >> are documented explicitly. This doesn't mean as always uses the > >> same syntax as another assembler for the same architecture; for > >> example, we know of several incompatible versions of 680x0 > >> assembly language syntax. > > > >I don't know when this paragraph was written. > >Today's gnu as is pretty reasonable tool for assembler develpment. > >Decent macro capabilities etc... Likely, not on par with > >macro-assemblers of IBM mainframes or of VAX/VMS, but rather similar > >in capabilities to Microsoft's Masm or with nasm. > >Certainly it is far more complete tool than what would be neeaded to > >process gcc output into objects. > > While true, David's point stands. By far and away, usage of as(1) > is most common in a compiler pipeline. Where adding " -" to 'as' invocation string would be zero cost. Also, my impression is that nowadays 'as' is rarely use via pipe. Personally, I stopped using -pipe flag in gcc ~15 years ago. YMMV. > It is extremly rare > (other than for operating system processor initialization code > on Intel moving from real mode to long mode and for processor > exception and interrupt handling) for anyone to write > direct assembler code in modern software development environments. > I did it rather regularly in last May to July. Indeed, it was nor "a real work" but hobby project.
[toc] | [prev] | [next] | [standalone]
| From | Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> |
|---|---|
| Date | 2026-09-22 01:53 +0800 |
| Message-ID | <nnd$12f31d84$6fdcd371@726cd1300fb9d43c> |
| In reply to | #402323 |
On 9/22/2026 1:41 AM, Michael S wrote: > On Sun, 20 Sep 2026 15:55:18 GMT > scott@slp53.sl.home (Scott Lurndal) wrote: > >> Michael S <already5chosen@yahoo.com> writes: >>> On Fri, 18 Sep 2026 18:08:38 +0200 >>> David Brown <david.brown@hesbynett.no> wrote: >> >>>> """ >>>> as is primarily intended to assemble the output of the GNU C >>>> compiler "gcc" for use by the linker "ld". Nevertheless, we've >>>> tried to make as assemble correctly everything that other >>>> assemblers for the same machine would assemble. Any exceptions >>>> are documented explicitly. This doesn't mean as always uses the >>>> same syntax as another assembler for the same architecture; for >>>> example, we know of several incompatible versions of 680x0 >>>> assembly language syntax. >>> >>> I don't know when this paragraph was written. >>> Today's gnu as is pretty reasonable tool for assembler develpment. >>> Decent macro capabilities etc... Likely, not on par with >>> macro-assemblers of IBM mainframes or of VAX/VMS, but rather similar >>> in capabilities to Microsoft's Masm or with nasm. >>> Certainly it is far more complete tool than what would be neeaded to >>> process gcc output into objects. >> >> While true, David's point stands. By far and away, usage of as(1) >> is most common in a compiler pipeline. > > Where adding " -" to 'as' invocation string would be zero cost. > Also, my impression is that nowadays 'as' is rarely use via pipe. > Personally, I stopped using -pipe flag in gcc ~15 years ago. > YMMV. > >> It is extremly rare >> (other than for operating system processor initialization code >> on Intel moving from real mode to long mode and for processor >> exception and interrupt handling) for anyone to write >> direct assembler code in modern software development environments. >> > > I did it rather regularly in last May to July. > Indeed, it was nor "a real work" but hobby project. > > Not a project, but recently I submitted a pre-screening questionnaire for a job [1] where I was expected to know RISC-V. Fortunately, I was able to use my knowledge of SPIM compatible cores [2], and answer cor- rectly. Point being, assembly programming should be considered /part of the job/, even if said job never has any "direct assembly" done. I can write more about that in a different followup. Best wishes, and happy assembly programming in comp.lang.c! [1] Not a batch job, but a labor job. [2] The trademark is irrelevant. -- Johann | email: invalid -> com | http://www.myrkraverk.com/blog/ I'm not from the Internet, I just work there. | via XS News https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2026-09-22 11:28 +0200 |
| Message-ID | <118thn3$mjfv$1@dont-email.me> |
| In reply to | #402323 |
On 21/09/2026 19:41, Michael S wrote: > On Sun, 20 Sep 2026 15:55:18 GMT > scott@slp53.sl.home (Scott Lurndal) wrote: > >> Michael S <already5chosen@yahoo.com> writes: >>> On Fri, 18 Sep 2026 18:08:38 +0200 >>> David Brown <david.brown@hesbynett.no> wrote: >> >>>> """ >>>> as is primarily intended to assemble the output of the GNU C >>>> compiler "gcc" for use by the linker "ld". Nevertheless, we've >>>> tried to make as assemble correctly everything that other >>>> assemblers for the same machine would assemble. Any exceptions >>>> are documented explicitly. This doesn't mean as always uses the >>>> same syntax as another assembler for the same architecture; for >>>> example, we know of several incompatible versions of 680x0 >>>> assembly language syntax. >>> >>> I don't know when this paragraph was written. >>> Today's gnu as is pretty reasonable tool for assembler develpment. >>> Decent macro capabilities etc... Likely, not on par with >>> macro-assemblers of IBM mainframes or of VAX/VMS, but rather similar >>> in capabilities to Microsoft's Masm or with nasm. >>> Certainly it is far more complete tool than what would be neeaded to >>> process gcc output into objects. >> >> While true, David's point stands. By far and away, usage of as(1) >> is most common in a compiler pipeline. > > Where adding " -" to 'as' invocation string would be zero cost. Changing things always has a non-zero cost, especially for long-established programs that are used by other programs or in scripts, makefiles, etc. Requiring " - " to use stdin would have been zero cost when development "as" was started (or perhaps when development of older assemblers were started, before "as" copied their functionality). But changing things later could break things for no appreciable gain. > Also, my impression is that nowadays 'as' is rarely use via pipe. > Personally, I stopped using -pipe flag in gcc ~15 years ago. > YMMV. Fair enough. I don't have "-pipe" in current makefiles either. I think it used to make a bit of difference to the speed, but on my current hardware / OS's / toolchain versions, there is no measurable difference. > >> It is extremly rare >> (other than for operating system processor initialization code >> on Intel moving from real mode to long mode and for processor >> exception and interrupt handling) for anyone to write >> direct assembler code in modern software development environments. >> > > I did it rather regularly in last May to July. > Indeed, it was nor "a real work" but hobby project. > Sure, people /do/ use "as" directly for assembly code. But in comparison to its use in connection with a compiler, it is "extremely rare". You are just one of these rarities :-)
[toc] | [prev] | [next] | [standalone]
| From | bart <bc@freeuk.com> |
|---|---|
| Date | 2026-09-22 11:34 +0100 |
| Message-ID | <118tlk6$p644$1@dont-email.me> |
| In reply to | #402330 |
On 22/09/2026 10:28, David Brown wrote: > On 21/09/2026 19:41, Michael S wrote: >> On Sun, 20 Sep 2026 15:55:18 GMT >> scott@slp53.sl.home (Scott Lurndal) wrote: >> >>> Michael S <already5chosen@yahoo.com> writes: >>>> On Fri, 18 Sep 2026 18:08:38 +0200 >>>> David Brown <david.brown@hesbynett.no> wrote: >>> >>>>> """ >>>>> as is primarily intended to assemble the output of the GNU C >>>>> compiler "gcc" for use by the linker "ld". Nevertheless, we've >>>>> tried to make as assemble correctly everything that other >>>>> assemblers for the same machine would assemble. Any exceptions >>>>> are documented explicitly. This doesn't mean as always uses the >>>>> same syntax as another assembler for the same architecture; for >>>>> example, we know of several incompatible versions of 680x0 >>>>> assembly language syntax. >>>> >>>> I don't know when this paragraph was written. >>>> Today's gnu as is pretty reasonable tool for assembler develpment. >>>> Decent macro capabilities etc... Likely, not on par with >>>> macro-assemblers of IBM mainframes or of VAX/VMS, but rather similar >>>> in capabilities to Microsoft's Masm or with nasm. >>>> Certainly it is far more complete tool than what would be neeaded to >>>> process gcc output into objects. >>> >>> While true, David's point stands. By far and away, usage of as(1) >>> is most common in a compiler pipeline. >> >> Where adding " -" to 'as' invocation string would be zero cost. > > Changing things always has a non-zero cost, especially for long- > established programs that are used by other programs or in scripts, > makefiles, etc. Requiring " - " to use stdin would have been zero cost > when development "as" was started (or perhaps when development of older > assemblers were started, before "as" copied their functionality). But > changing things later could break things for no appreciable gain. I believe the original 'as' was from 1971, and the GNU version fro 1986. You'd think that "-" as an option could have been added at some point, and default stdin deprecated. Or the GNU version could have been called 'gas' with the new behaviour, while still providing 'as'. Modifying gcc's internal invocation string to either add "-" or to use 'gas' instead would have been utterly trivial. >> I did it rather regularly in last May to July. >> Indeed, it was nor "a real work" but hobby project. >> > > Sure, people /do/ use "as" directly for assembly code. But in > comparison to its use in connection with a compiler, it is "extremely > rare". You are just one of these rarities :-) Well, /I/ used it last year. I had reasons for not using it via gcc. One was to ensure my generated GAS could be assembled by a standalone 'as' product. And presumably people use make use of its default stdin for piping: x > as > y If this is uncommon, then there's even less point to the feature.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2026-09-22 15:00 +0000 |
| Message-ID | <3KwsS.87967$5X3.13390@fx12.iad> |
| In reply to | #402331 |
bart <bc@freeuk.com> writes: >On 22/09/2026 10:28, David Brown wrote: >> >> Changing things always has a non-zero cost, especially for long- >> established programs that are used by other programs or in scripts, >> makefiles, etc. Requiring " - " to use stdin would have been zero cost >> when development "as" was started (or perhaps when development of older >> assemblers were started, before "as" copied their functionality). But >> changing things later could break things for no appreciable gain. > >I believe the original 'as' was from 1971, and the GNU version fro 1986. > >You'd think that "-" as an option could have been added at some point, >and default stdin deprecated. Since you're the only person whom I have ever heard complain about it, it is highly unlikely that anyone would have changed it "at some point" just to make you happy.
[toc] | [prev] | [next] | [standalone]
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Date | 2026-09-22 14:22 +0000 |
| Message-ID | <118u2uc$tsif$1@dont-email.me> |
| In reply to | #402330 |
On Tue, 22 Sep 2026 11:28:03 +0200, David Brown wrote: > On 21/09/2026 19:41, Michael S wrote: >> On Sun, 20 Sep 2026 15:55:18 GMT >> scott@slp53.sl.home (Scott Lurndal) wrote: [snip] >>> While true, David's point stands. By far and away, usage of as(1) >>> is most common in a compiler pipeline. >> >> Where adding " -" to 'as' invocation string would be zero cost. > > Changing things always has a non-zero cost, especially for > long-established programs that are used by other programs or in scripts, > makefiles, etc. Requiring " - " to use stdin would have been zero cost > when development "as" was started Given the Unix origins of "as", I would ascribe a trivial, but non-zero cost to the inclusion of an " - " flag. as(1), as originally developed, would have had stdin already open and ready for use at process startup. However, the parsing of a flag, even as trivial as an " - " flag, costs some lines of code, and a few unnecessary CPU cycles on each run. Trivial, yes, but not "zero cost". [snip] -- Lew Pitcher "In Skills We Trust" Not LLM output - I'm just like this.
[toc] | [prev] | [next] | [standalone]
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Date | 2026-09-22 15:04 +0000 |
| Message-ID | <118u5eh$tsif$2@dont-email.me> |
| In reply to | #402333 |
On Tue, 22 Sep 2026 14:22:05 +0000, Lew Pitcher wrote:
> On Tue, 22 Sep 2026 11:28:03 +0200, David Brown wrote:
>
>> On 21/09/2026 19:41, Michael S wrote:
>>> On Sun, 20 Sep 2026 15:55:18 GMT
>>> scott@slp53.sl.home (Scott Lurndal) wrote:
> [snip]
>>>> While true, David's point stands. By far and away, usage of as(1)
>>>> is most common in a compiler pipeline.
>>>
>>> Where adding " -" to 'as' invocation string would be zero cost.
>>
>> Changing things always has a non-zero cost, especially for
>> long-established programs that are used by other programs or in scripts,
>> makefiles, etc. Requiring " - " to use stdin would have been zero cost
>> when development "as" was started
>
> Given the Unix origins of "as", I would ascribe a trivial, but non-zero
> cost to the inclusion of an " - " flag.
>
> as(1), as originally developed, would have had stdin already open and ready
> for use at process startup.
OK, I'm going to correct myself here. as(1), as originally developed, appeared
in Unix before the advent of pipes, so the original would /not/ have stdin
already open and usable. I'm not fluent in PDP-7 or PDP-11 assembly language
(the language as(1) was coded in up until Unix Version 8), so I won't speculate
on /what/ the original as(1) did instead.
By Unix Version 8, as(1) had been recoded in C ("Copyright (c) 1980 Regents of
the University of California"), and allowed (perhaps inadvertantly) for a " - "
flag. I say "inadvertantly" because the code strips the leading dash off of
each argument before parsing it, as a argument compatibility step between itself
and the older versions
"/*
* We can throw away single minus signs, so
* that make scripts for the PDP 11 assembler work
* on this assembler too
*/"
So, by the time V8 Unix appeared, as(1) accepted " - " as a no-op, and defaulted
input to stdin unless assembly source files were listed as unflagged arguments.
> However, the parsing of a flag, even as trivial
> as an " - " flag, costs some lines of code, and a few unnecessary CPU cycles
> on each run. Trivial, yes, but not "zero cost".
>
> [snip]
--
Lew Pitcher
"In Skills We Trust"
Not LLM output - I'm just like this.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2026-09-22 16:38 +0000 |
| Message-ID | <oaysS.303891$7nI1.231433@fx02.iad> |
| In reply to | #402338 |
Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:
>On Tue, 22 Sep 2026 14:22:05 +0000, Lew Pitcher wrote:
>
>> On Tue, 22 Sep 2026 11:28:03 +0200, David Brown wrote:
>>
>>> On 21/09/2026 19:41, Michael S wrote:
>>>> On Sun, 20 Sep 2026 15:55:18 GMT
>>>> scott@slp53.sl.home (Scott Lurndal) wrote:
>> [snip]
>>>>> While true, David's point stands. By far and away, usage of as(1)
>>>>> is most common in a compiler pipeline.
>>>>
>>>> Where adding " -" to 'as' invocation string would be zero cost.
>>>
>>> Changing things always has a non-zero cost, especially for
>>> long-established programs that are used by other programs or in scripts,
>>> makefiles, etc. Requiring " - " to use stdin would have been zero cost
>>> when development "as" was started
>>
>> Given the Unix origins of "as", I would ascribe a trivial, but non-zero
>> cost to the inclusion of an " - " flag.
>>
>> as(1), as originally developed, would have had stdin already open and ready
>> for use at process startup.
>
>OK, I'm going to correct myself here. as(1), as originally developed, appeared
>in Unix before the advent of pipes, so the original would /not/ have stdin
>already open and usable. I'm not fluent in PDP-7 or PDP-11 assembly language
>(the language as(1) was coded in up until Unix Version 8), so I won't speculate
>on /what/ the original as(1) did instead.
In Unix v1, as was a two pass program (a1 and a2) which stored the intermediate
representation in disk files.
Here's the start code for the first pass [cmd/as19.s] (my annotation)
start:
sys intr; aexit
mov sp,r5 /* Points to ARGC */
mov (r5)+,r0 /* Load ARGC in R0, Update R5 to point to ARGV[0] */
cmpb *2(r5),$'- /* If argument starts with '-' */
bne 1f /* skip forward to label 1 if not */
tst (r5)+ /* Increment ARGV by 1 */
dec r0 /* Decrement the argument count by 1 */
br 2f
1:
clr unglob
2:
movb r0,nargs /* save argument count */
mov r5,curarg /* save pointer to argument */
jsr r5,fcreat; a.tmp1
movb r0,pof
jsr r5,fcreat; a.tmp2 /* Create two temporary files (a.tmp1, a.tmp2) (a.tmp3 is
created later) */
movb r0,fbfil
jsr pc,setup /* Initialize symbol table, etc */
mov $1,r0 /* stdout file descriptor to pass to 'write' */
sys write; qi; 2 /* Write upper-case 'I' to stdout */
jmp go
Then it starts parsing the input treating the remaining arguments
as filenames and reading from each in turn.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-09-30 02:28 +0000 |
| Message-ID | <119hs42$3r0er$5@dont-email.me> |
| In reply to | #402338 |
On Tue, 22 Sep 2026 15:04:50 -0000 (UTC), Lew Pitcher wrote:
> OK, I'm going to correct myself here. as(1), as originally
> developed, appeared in Unix before the advent of pipes, so the
> original would /not/ have stdin already open and usable. I'm not
> fluent in PDP-7 or PDP-11 assembly language (the language as(1) was
> coded in up until Unix Version 8), so I won't speculate on /what/
> the original as(1) did instead.
There is a project to resurrect the original PDP-7 “Unix v0” and get
it running again <https://github.com/DoctorWkt/pdp7-unix>.
Looking at the file as.s, I found this “init” routine:
init: 0 " common init for both passes
lac i 017777
dac narg " save arg count
lac 017777
tad d1
dac fname " point to first file name
...
That 0 word at the start is for holding the return address (Stack?
What stack?). Then a word is fetched from the address stored at the
location 017777 (octal, obviously; and “i” for “indirect”), and this
is argc. The next word after that is the first entry in argv (“d1” is
just a location containing the constant 1).
So the argv/argc mechanism is already in existence, even if without
pipes, so files must be explicitly opened.
There is some peculiarity with how filenames are managed: there seems
to be 4 words reserved before the start of each filename which has
some use by the “sys open” call.
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2026-10-06 01:29 +0000 |
| Message-ID | <11a1iub$3u6ge$4@paganini.bofh.team> |
| In reply to | #402307 |
Scott Lurndal <scott@slp53.sl.home> wrote:
> Michael S <already5chosen@yahoo.com> writes:
>>On Fri, 18 Sep 2026 18:08:38 +0200
>>David Brown <david.brown@hesbynett.no> wrote:
>
>>> """
>>> as is primarily intended to assemble the output of the GNU C compiler
>>> "gcc" for use by the linker "ld". Nevertheless, we've tried to make
>>> as assemble correctly everything that other assemblers for the same
>>> machine would assemble. Any exceptions are documented explicitly.
>>> This doesn't mean as always uses the same syntax as another assembler
>>> for the same architecture; for example, we know of several
>>> incompatible versions of 680x0 assembly language syntax.
>>>
>>
>>I don't know when this paragraph was written.
>>Today's gnu as is pretty reasonable tool for assembler develpment.
>>Decent macro capabilities etc... Likely, not on par with
>>macro-assemblers of IBM mainframes or of VAX/VMS, but rather similar in
>>capabilities to Microsoft's Masm or with nasm.
>>Certainly it is far more complete tool than what would be neeaded to
>>process gcc output into objects.
>
> While true, David's point stands. By far and away, usage of as(1)
> is most common in a compiler pipeline. It is extremly rare
> (other than for operating system processor initialization code
> on Intel moving from real mode to long mode and for processor
> exception and interrupt handling) for anyone to write
> direct assembler code in modern software development environments.
In my experience main need for assembly is in language runtimes
and in high performance computational kernels. It is tiny
fraction of all code around, but significantly more than what
is needed for interrupt stubs (rest of handler can be in C) and
processor mode switching. As an example, one language that I use
and maintain needs about 2800 lines of assembly per architecture.
This is down from about 6000 lines required in earlier versions.
Difference is partially from using macros to generate repeated
assembly sequences, partially (more) from delegation more of
runtime support to C. However, more assembly could improve
performance, so this amount may grow again. Comparably,
rest of language implementation, bundled libraries and tools
is between 0.5 and 1 MLOC. So assembler code is small but
vital part. And when porting code generators essentially need
assembly sequences which correspond to language constructs.
The rest of high-level code needs minor adjustment, so porting
is mostly at assembly level.
A few other systems have similar characteristics, so I do not
think that the above is an isolated example.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2026-09-19 22:01 +0300 |
| Message-ID | <20260919220132.0000185d@yahoo.com> |
| In reply to | #402241 |
On Fri, 18 Sep 2026 18:08:38 +0200 David Brown <david.brown@hesbynett.no> wrote: > > > On the other hand, I have a number of times run a "grep" command and > wondered why it was taking so long - because I'd forgotten to give it > the files to search! (That's my fault, not grep's.) > I don't recollect that it ever happened to me. I'd guess the reson is that it only happens when grep is given exactly 1 parameter, whch is less likely to happen by mistake than calling it with no parameters.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2026-09-18 20:28 +0000 |
| Message-ID | <E9hrS.293115$7nI1.167498@fx02.iad> |
| In reply to | #402237 |
Michael S <already5chosen@yahoo.com> writes:
>On Fri, 18 Sep 2026 15:28:21 GMT
>scott@slp53.sl.home (Scott Lurndal) wrote:
>
>> Michael S <already5chosen@yahoo.com> writes:
>> >On Thu, 17 Sep 2026 17:50:57 -0700
>> >Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>> >
>> >> bart <bc@freeuk.com> writes:
>> >> > On 18/09/2026 01:04, Steven G. Kargl wrote:
>> >> [...]
>> >> >> Most people read (or at least skim) the documentation
>> >> >> that comes with the software they use.
>> >> >
>> >> > Most people probably don't. They will try running such programs
>> >> > without input, as often that gives usage info.
>> >>
>> >> [...]
>> >>
>> >> You've seen how that approach fails.
>> >>
>> >> There are valid reasons for the way "as" behaves.
>> >
>> >Well, if you consider compatibility with weird notion of "user
>> >interface" of its original creator as a valid reason, then yes.
>> >Even I accept it as valid.
>> >Which does not make it less bad in the absolute sense.
>> >Desire to give to user an option to accept an input from standard
>> >input by itself is not unreasonable, bit it should be an option
>> >rather than default.
>>
>> That's your opinion. That's not the unix philosophy. Many
>> unix commands default to stdin if no file name is specified
>> (specifically to support streaming the output of one command
>> to the input of another).
>
>There is big difference between utilities like grep or sort and
>something like as. Blindly treating them as the same is wrong.
Historically speaking, as(1) was part of the c compiler pipeline
accepting the output of the
cpp file.c | c0 | c1 | c2 | as > file.o
From v6 C c20.c:
if (argc>1) {
if ((fin = open(argv[1], 0)) < 0) {
printf("C2: can't find %s\n", argv[1]);
exit(1);
}
} else
fin = dup(0);
if (argc>2) {
if ((fout = creat(argv[2], 0666)) < 0) {
fout = 1;
printf("C2: can't create %s\n", argv[2]);
exit(1);
}
} else
fout = dup(1);
[toc] | [prev] | [next] | [standalone]
| From | "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> |
|---|---|
| Date | 2026-09-18 05:42 +0000 |
| Message-ID | <118ij09$vgev$1@dont-email.me> |
| In reply to | #402199 |
On Fri, 18 Sep 2026 01:34:12 +0100, bart wrote: > On 18/09/2026 01:04, Steven G. Kargl wrote: >> On Thu, 17 Sep 2026 20:54:35 +0100, bart wrote: >> >>> Most command-line compilers give you version and help info when no >>> parameters follow. But at least it says something; try this: >>> >>> c:\c\as >>> >>> and it apparently hangs (it's waiting for you type an assembly program >>> from the console!) >>> >> >> Most people read (or at least skim) the documentation >> that comes with the software they use. > > Most people probably don't. Touche. As a gfortran contributor, I'm well-aware of the fact that users lack reading abilities. > They will try running such programs without > input, as often that gives usage info. Not on a Unix(-like) system. Many tools will fall-back to accepting stdin for input. It's essentially how pipes on a command line work. May Microsoft doesn't know how to use pipes? > 'as' is more peculiar than most assemblers: > > * It takes input from stdin as default > > * The output, even on Windows, is a file called a.out > > * If given two or more input files, these are literally concatenated > into one ASM file. More typically there is one object file produced per file > > >> % man as > > 'man' doesn't exist on Windows. Well, this is your problem. Why are you using Window? :-) (and, no, linux is not the answer.) If 'man' doesn't exist on windows, google 'GNU as manual'. You might learn how to use the tool should work. > Using 'as --help' gives lots of > complicated options that will mean little to some who has not used this > before and simply wants to turn file.s into file.o. > > This is my assembler for example when I type its name: > > c:\c>aa > AA7 Assembler 29-Aug-2026 > Usage: > aa filename[.asm] # Assemble filename.asm to filename.exe > aa -help # Show other options > > Simple, yes? I suppose it's simply if one doesn't want to enter an assembly program at the command line. % as .text; .p2align 4,0x90; .globl sqrt; .type sqrt,@function; sqrt:; .cfi_startproc fldl 4(%esp) fsqrt ret .size sqrt, . - sqrt; .cfi_endproc .section .note.GNU-stack,"",%progbits % nm a.out 0000000000000000 T sqrt or one can do % cat z.s .text; .p2align 4,0x90; .globl sqrt; .type sqrt,@function; sqrt:; .cfi_startproc fldl 4(%esp) fsqrt ret .size sqrt, . - sqrt; .cfi_endproc .section .note.GNU-stack,"",%progbits % cat z.s | as % nm a.out 0000000000000000 T sqrt -- steve
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2026-09-18 08:08 +0200 |
| Message-ID | <118ikgv$scqh$1@dont-email.me> |
| In reply to | #402205 |
On 2026-09-18 07:42, Steven G. Kargl wrote:
> On Fri, 18 Sep 2026 01:34:12 +0100, bart wrote:
>
>> On 18/09/2026 01:04, Steven G. Kargl wrote:
>>> On Thu, 17 Sep 2026 20:54:35 +0100, bart wrote:
>>>
>>>> Most command-line compilers give you version and help info when no
>>>> parameters follow. But at least it says something; try this:
>>>>
>>>> c:\c\as
>>>>
>>>> and it apparently hangs (it's waiting for you type an assembly program
>>>> from the console!)
>>>>
>>>
>>> Most people read (or at least skim) the documentation
>>> that comes with the software they use.
>>
>> Most people probably don't.
>
> Touche. As a gfortran contributor, I'm well-aware of
> the fact that users lack reading abilities.
>
>> They will try running such programs without
>> input, as often that gives usage info.
>
> Not on a Unix(-like) system. Many tools will fall-back to accepting
> stdin for input. It's essentially how pipes on a command line
> work. May Microsoft doesn't know how to use pipes?
>
>> 'as' is more peculiar than most assemblers:
>>
>> * It takes input from stdin as default
>>
>> * The output, even on Windows, is a file called a.out
>>
>> * If given two or more input files, these are literally concatenated
>> into one ASM file. More typically there is one object file produced per file
>>
>>
>>> % man as
>>
>> 'man' doesn't exist on Windows.
>
> Well, this is your problem. Why are you using Window? :-)
> (and, no, linux is not the answer.)
>
> If 'man' doesn't exist on windows, google 'GNU as manual'.
> You might learn how to use the tool should work.
>
>> Using 'as --help' gives lots of
>> complicated options that will mean little to some who has not used this
>> before and simply wants to turn file.s into file.o.
>>
>> This is my assembler for example when I type its name:
>>
>> c:\c>aa
>> AA7 Assembler 29-Aug-2026
>> Usage:
>> aa filename[.asm] # Assemble filename.asm to filename.exe
>> aa -help # Show other options
>>
>> Simple, yes?
>
> I suppose it's simply if one doesn't want to enter
> an assembly program at the command line.
>
> % as
> .text;
> .p2align 4,0x90;
> .globl sqrt;
> .type sqrt,@function;
> sqrt:;
> .cfi_startproc
> fldl 4(%esp)
> fsqrt
> ret
> .size sqrt, . - sqrt; .cfi_endproc
>
> .section .note.GNU-stack,"",%progbits
> % nm a.out
> 0000000000000000 T sqrt
>
> or one can do
>
> % cat z.s
> .text;
> .p2align 4,0x90;
> .globl sqrt;
> .type sqrt,@function;
> sqrt:;
> .cfi_startproc
> fldl 4(%esp)
> fsqrt
> ret
> .size sqrt, . - sqrt; .cfi_endproc
>
> .section .note.GNU-stack,"",%progbits
>
> % cat z.s | as
> % nm a.out
> 0000000000000000 T sqrt
>
Note that it's unlikely (and thus IMO a bad example) that assembly code
is entered on the command line.
Note also that your pipe example is not convincing since if the program
is already in a file ("z.s") you don't need a pipe.
(BTW, you also don't need 'cat' in your example since "as < z.s" would
suffice if you intend to use the standard input channel instead of a
file.)
I think a better explanation for 'as' accepting data from standard input
would be the cases where some higher level languages create assembly
data on standard output; as in "c-comp | as" or "pas-comp | as" .
(But, probably most important for this thread; whatever we explain, the
one you've been replying to is mentally resistant to such explanation
as they don't fit his mental image and capabilities (or willingness) to
think beyond.)
Janis
[toc] | [prev] | [next] | [standalone]
| From | bart <bc@freeuk.com> |
|---|---|
| Date | 2026-09-18 10:23 +0100 |
| Message-ID | <118ivv4$14rfu$1@dont-email.me> |
| In reply to | #402205 |
On 18/09/2026 06:42, Steven G. Kargl wrote:
> On Fri, 18 Sep 2026 01:34:12 +0100, bart wrote:
>> This is my assembler for example when I type its name:
>>
>> c:\c>aa
>> AA7 Assembler 29-Aug-2026
>> Usage:
>> aa filename[.asm] # Assemble filename.asm to filename.exe
>> aa -help # Show other options
>>
>> Simple, yes?
>
> I suppose it's simply if one doesn't want to enter
> an assembly program at the command line.
Why do that when you can just use a text editor first? The chances are
there will be errors and typos and then you just edit the file; how do
you edit?
Do you routinely type C code that way?
And then, what happens to the source code of that program; is it just lost?
If 'as' accepts stdin input then it will be primarily to support piping
where the asm source has been machine-generated.
Most command-line language tools that take in source will use text files
as input.
> % as
> .text;
> .p2align 4,0x90;
> .globl sqrt;
> .type sqrt,@function;
> sqrt:;
> .cfi_startproc
> fldl 4(%esp)
> fsqrt
> ret
> .size sqrt, . - sqrt; .cfi_endproc
>
> .section .note.GNU-stack,"",%progbits
Here's my version (this is for x64 using XMM regs on Win64 ABI, with a
'main' routine to call it):
sqrt::
sqrtsd xmm0, xmm0
ret
main::
sub rsp, 40
mov xmm0, [two]
call sqrt
mov xmm1, xmm0
movq rdx, xmm0
mov rcx, fmt
call printf*
add rsp, 40
ret
isegment
two:
dq 2.0
fmt:
db "%f", 0
This is my assembler in action:
c:\ax>aa -r test
Assembling test.asm to test.(run)
1.414214
The -r tells it to run the program immediately. Otherwise it generates
an executable:
c:\ax>aa test
Assembling test.asm to test.exe
c:\ax>test
1.414214
Notice I only had to type two 'aa test'; I don't even need the
extension. 'aa' is super-smart and knows it is an assembler!
With 'as', and with a version in GAS format, I'd need to do:
as test.asm -o test.obj && gcc test.obj -o test
This produces a 53KB file (18KB if I add -s). The aa version is 2.5KB.
You can see that my versions, both assembly source and how it is
invoked, are much cleaner and simpler. ('aa' does not need a linker.)
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2026-09-18 15:24 +0000 |
| Message-ID | <5JcrS.84457$ZAne.37914@fx48.iad> |
| In reply to | #402199 |
bart <bc@freeuk.com> writes: >On 18/09/2026 01:04, Steven G. Kargl wrote: >> On Thu, 17 Sep 2026 20:54:35 +0100, bart wrote: >> >>> Most command-line compilers give you version and help info when no >>> parameters follow. But at least it says something; try this: >>> >>> c:\c\as >>> >>> and it apparently hangs (it's waiting for you type an assembly program >>> from the console!) >>> >> >> Most people read (or at least skim) the documentation >> that comes with the software they use. > >Most people probably don't. They will try running such programs without >input, as often that gives usage info. Please try to speak for yourself. Those familiar with unix would understand implicitly, as many commands will read from stdin if no filename is specified. > >'man' doesn't exist on Windows. So, use a web browser. https://man7.org/linux/man-pages/man1/as.1.html
[toc] | [prev] | [next] | [standalone]
| From | bart <bc@freeuk.com> |
|---|---|
| Date | 2026-09-18 16:31 +0100 |
| Message-ID | <118jlgl$1dls4$1@dont-email.me> |
| In reply to | #402233 |
On 18/09/2026 16:24, Scott Lurndal wrote: > bart <bc@freeuk.com> writes: >> On 18/09/2026 01:04, Steven G. Kargl wrote: >>> On Thu, 17 Sep 2026 20:54:35 +0100, bart wrote: >>> >>>> Most command-line compilers give you version and help info when no >>>> parameters follow. But at least it says something; try this: >>>> >>>> c:\c\as >>>> >>>> and it apparently hangs (it's waiting for you type an assembly program >>>> from the console!) >>>> >>> >>> Most people read (or at least skim) the documentation >>> that comes with the software they use. >> >> Most people probably don't. They will try running such programs without >> input, as often that gives usage info. > > Please try to speak for yourself. > > Those familiar with unix would understand implicitly, as many > commands will read from stdin if no filename is specified. So how do they tell whether a program is hanging, or is waiting for input? FFS would it hurt to print a message showing what is expected? It is exasperating that people defend such poor UIs.
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2026-09-18 11:29 -0700 |
| Message-ID | <118jvtr$1grii$3@kst.eternal-september.org> |
| In reply to | #402236 |
bart <bc@freeuk.com> writes:
> On 18/09/2026 16:24, Scott Lurndal wrote:
[...]
>> Those familiar with unix would understand implicitly, as many
>> commands will read from stdin if no filename is specified.
> So how do they tell whether a program is hanging, or is waiting for input?
By typing Control-D.
> FFS would it hurt to print a message showing what is expected?
Yes, it would. I won't offer an explanation because you would not care
about it or admit that you understand it.
> It is exasperating that people defend such poor UIs.
It is exasperating *to you* that people try to *explain* UIs that you
dislike.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | bart <bc@freeuk.com> |
|---|---|
| Date | 2026-09-18 20:14 +0100 |
| Message-ID | <118k2il$1jgd3$1@dont-email.me> |
| In reply to | #402245 |
On 18/09/2026 19:29, Keith Thompson wrote: > bart <bc@freeuk.com> writes: >> On 18/09/2026 16:24, Scott Lurndal wrote: > [...] >>> Those familiar with unix would understand implicitly, as many >>> commands will read from stdin if no filename is specified. >> So how do they tell whether a program is hanging, or is waiting for input? > > By typing Control-D. How would they know without a message? But suppose they did that, what happens, the program stops? What if it was just busy; wouldn't Ctrl-D screw it up? >> FFS would it hurt to print a message showing what is expected? > > Yes, it would. I won't offer an explanation because you would not care > about it or admit that you understand it. Try me. (In my last post I showed an example of my C compiler taking input from stdin (requested, not as default!) and it displays a message. The world is still turning.
[toc] | [prev] | [next] | [standalone]
Page 16 of 25 — ← Prev page 1 … 14 15 [16] 17 18 … 25 Next page →
Back to top | Article view | comp.lang.c
csiph-web