Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #392008 > unrolled thread
| Started by | Thiago Adams <thiago.adams@gmail.com> |
|---|---|
| First post | 2025-04-04 16:23 -0300 |
| Last post | 2025-10-16 00:43 +0100 |
| Articles | 20 on this page of 698 — 31 participants |
Back to article view | Back to comp.lang.c
do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-04-04 16:23 -0300
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-04 21:18 +0100
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-04-04 17:31 -0300
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-04 20:34 +0000
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-04-04 17:37 -0300
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-04 21:01 +0000
Re: do { quit; } else { } "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-04-04 14:36 -0700
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-04 20:39 +0000
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-04-04 17:43 -0300
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-04-04 17:46 -0300
Re: do { quit; } else { } candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-04-08 19:00 +0000
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-05 14:54 +0000
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-05 17:54 +0200
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-05 16:10 +0000
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-05 23:37 +0200
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-06 14:41 +0000
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-06 10:52 +0300
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-06 14:45 +0000
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-04 13:48 -0700
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-04-04 17:58 -0300
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-06 05:47 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-06 16:13 +0300
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-06 07:32 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-06 19:03 +0300
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-07 05:45 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-07 21:02 +0300
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-07 19:31 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-08 10:12 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-08 12:35 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-08 16:50 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-08 17:28 +0100
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-08 10:32 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-08 19:04 +0100
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-08 14:18 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-08 23:38 +0100
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-08 16:27 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-09 01:02 +0100
Re: do { quit; } else { } "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-04-08 22:55 -0700
Re: do { quit; } else { } "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-04-08 22:56 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-09 15:07 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-10 00:49 +0100
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-10 00:20 +0000
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-10 12:08 +0300
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-10 16:23 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-10 12:00 +0100
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 04:28 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-10 14:34 +0100
Endless complaints [was Re: do { quit; } else { }] scott@slp53.sl.home (Scott Lurndal) - 2025-04-10 14:33 +0000
Re: Endless complaints [was Re: do { quit; } else { }] bart <bc@freeuk.com> - 2025-04-10 16:12 +0100
Re: Endless complaints [was Re: do { quit; } else { }] Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-11 00:18 +0200
Re: Endless complaints [was Re: do { quit; } else { }] bart <bc@freeuk.com> - 2025-04-11 00:10 +0100
Re: Endless complaints [was Re: do { quit; } else { }] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 17:41 -0700
Re: Endless complaints [was Re: do { quit; } else { }] Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-11 02:45 +0000
Re: Endless complaints [was Re: do { quit; } else { }] David Brown <david.brown@hesbynett.no> - 2025-04-11 10:14 +0200
Re: Endless complaints [was Re: do { quit; } else { }] bart <bc@freeuk.com> - 2025-04-11 12:32 +0100
Re: Endless complaints [was Re: do { quit; } else { }] Michael S <already5chosen@yahoo.com> - 2025-04-11 14:50 +0300
Re: Endless complaints [was Re: do { quit; } else { }] bart <bc@freeuk.com> - 2025-04-11 12:56 +0100
Re: Endless complaints [was Re: do { quit; } else { }] Michael S <already5chosen@yahoo.com> - 2025-04-11 15:12 +0300
Re: Endless complaints [was Re: do { quit; } else { }] Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-11 15:12 +0200
Re: Endless complaints [was Re: do { quit; } else { }] bart <bc@freeuk.com> - 2025-04-11 15:55 +0100
Re: Endless complaints [was Re: do { quit; } else { }] David Brown <david.brown@hesbynett.no> - 2025-04-11 15:02 +0200
Re: Endless complaints Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-11 10:03 -0700
Re: Endless complaints [was Re: do { quit; } else { }] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 12:26 -0700
Re: Endless complaints [was Re: do { quit; } else { }] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 15:27 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 15:23 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-11 00:49 +0100
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 17:59 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-11 14:26 +0300
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-11 16:11 +0200
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-11 17:22 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-11 20:46 +0100
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 14:10 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-13 20:45 +0300
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-11 19:05 -0700
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-12 16:37 +0200
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-12 13:25 -0700
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-13 11:40 +0200
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-13 20:17 -0400
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-13 17:51 -0700
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-13 22:23 -0400
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-14 11:07 +0200
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-05-14 15:03 +0000
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-14 23:17 -0400
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-14 11:22 +0200
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-13 18:15 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 11:20 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-05 16:12 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-05 16:36 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-05 17:01 -0700
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-10 16:51 +0000
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-10 18:31 +0000
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-10 19:14 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-10 19:36 +0100
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-10 19:29 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-11 00:02 +0100
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-10 18:52 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 20:51 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-10 22:55 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 23:00 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-11 12:14 +0100
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-04 22:01 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 21:20 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 21:22 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 21:24 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-10 20:11 +0100
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-11 10:07 -0700
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 16:25 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 15:38 +0100
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 16:42 +0200
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-09 17:43 +0200
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-13 19:34 -0700
Re: do { quit; } else { } Richard Damon <richard@damon-family.org> - 2025-04-09 07:15 -0400
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-09 13:51 +0200
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-09 11:42 +0200
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-09 13:04 +0300
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-09 14:06 +0200
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-11 12:27 -0400
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-09 13:11 +0300
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-09 14:11 +0200
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-09 13:16 +0300
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-09 14:24 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-09 11:51 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-09 14:36 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-09 14:13 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-09 16:00 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-09 16:37 +0100
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-10 20:40 -0400
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-11 12:20 -0400
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-11 17:30 +0000
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-09 12:58 +0200
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-09 14:23 +0300
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-09 12:50 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-09 14:44 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-10 11:55 +0300
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-10 14:46 +0200
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-10 15:41 +0000
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-10 21:05 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-10 20:27 +0100
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-10 20:57 +0000
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-11 11:17 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-11 12:51 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-11 16:25 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-11 15:50 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-11 17:24 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-11 17:56 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-11 20:29 +0200
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 13:58 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-11 22:24 +0100
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 14:36 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 00:13 +0100
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 16:59 -0700
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 02:27 +0100
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 18:53 -0700
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-12 02:43 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 12:50 +0100
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-12 12:57 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 14:33 +0100
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-13 04:53 +0200
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-12 15:43 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 17:52 +0100
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-12 17:40 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-13 00:09 +0100
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-13 21:40 +0300
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-13 20:08 +0000
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-14 00:30 +0300
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-13 21:07 -0400
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-13 18:33 -0700
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-13 22:57 -0400
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-13 20:26 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-13 14:58 -0700
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-04-13 21:58 -0300
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-13 18:22 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-13 14:52 -0700
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-13 20:50 -0400
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 19:17 +0100
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-12 09:59 -0400
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 15:15 +0100
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-12 06:33 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 12:00 +0100
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-13 04:27 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-13 12:33 +0100
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-13 12:36 +0100
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-13 14:54 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-13 17:48 +0100
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-14 05:59 +0200
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-14 14:11 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-13 14:58 +0100
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-13 14:34 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-13 17:39 +0100
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-14 06:23 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-14 11:16 +0100
Re: do { quit; } else { } tTh <tth@none.invalid> - 2025-04-14 12:51 +0200
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-14 12:12 +0100
Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-14 14:18 +0200
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-14 15:33 +0300
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-14 16:22 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-15 09:17 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 11:30 +0100
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-15 15:34 +0300
Re: Loops (was Re: do { quit; } else { }) Richard Heathfield <rjh@cpax.org.uk> - 2025-04-15 13:51 +0100
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-04 07:40 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-04 07:31 -0700
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-05-04 18:08 +0300
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-05-05 10:42 +0300
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-10 06:43 -0700
Re: Loops (was Re: do { quit; } else { }) Muttley@dastardlyhq.com - 2025-05-10 15:56 +0000
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-05-10 17:48 +0000
Re: Loops (was Re: do { quit; } else { }) Muttley@dastardlyhq.com - 2025-05-11 08:20 +0000
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-10 14:29 -0700
Re: Loops (was Re: do { quit; } else { }) Muttley@dastardlyhq.com - 2025-05-11 08:21 +0000
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-05-11 12:02 +0200
Re: Loops (was Re: do { quit; } else { }) Muttley@dastardlyhq.com - 2025-05-11 15:30 +0000
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-05-11 16:29 +0000
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-05-11 18:49 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-11 14:41 -0700
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-11 17:43 -0400
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-11 15:06 -0700
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-11 18:30 -0400
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-11 18:15 -0700
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-11 19:09 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-12 00:16 -0700
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-12 02:23 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-12 07:19 -0700
Re: Loops (was Re: do { quit; } else { }) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-12 15:34 +0100
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-12 22:42 -0700
Re: Loops (was Re: do { quit; } else { }) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-13 07:31 +0100
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-14 21:12 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-13 09:30 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-13 22:28 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-12 13:31 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-14 20:44 -0700
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-14 21:45 -0700
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-05-12 17:24 +0200
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-12 00:07 -0400
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-12 00:43 -0700
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-12 02:27 -0700
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-05-12 17:18 +0200
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-01-28 09:54 -0800
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-01-28 16:42 -0800
Re: Loops (was Re: do { quit; } else { }) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-01-31 07:03 +0000
Re: Loops (was Re: do { quit; } else { }) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-01-31 03:53 +0000
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2026-01-31 18:26 +0200
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2026-01-31 18:33 +0000
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2026-01-31 21:02 +0200
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-12 19:53 -0400
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-12 23:03 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-12 19:04 -0700
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-05-12 17:08 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-12 13:38 -0700
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-05-13 12:41 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-13 23:16 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-13 14:35 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-13 15:10 -0700
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-13 15:41 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-13 18:38 -0700
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-13 19:37 -0700
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-13 23:54 -0400
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-13 21:19 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-13 21:12 -0700
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-13 22:38 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-03-01 21:55 -0800
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-03-01 23:37 -0800
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-05-14 03:35 +0000
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-13 21:54 -0700
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-05-14 06:31 +0000
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-06-10 06:01 -0700
Re: Loops (was Re: do { quit; } else { }) Bonita Montero <Bonita.Montero@gmail.com> - 2025-06-14 12:24 +0200
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-06-14 13:57 +0000
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-06-14 22:27 +0300
Re: Loops (was Re: do { quit; } else { }) Bonita Montero <Bonita.Montero@gmail.com> - 2025-06-15 09:32 +0200
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-05-14 13:00 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-14 13:20 +0200
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-05-14 23:20 -0400
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-05-15 11:23 +0200
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-01-06 13:55 -0800
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-11 17:59 -0700
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-05-12 10:11 +0000
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-05-12 17:09 +0300
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-05-11 01:09 +0300
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-11 17:30 -0700
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-05-12 16:18 +0300
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-14 11:09 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-13 15:57 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-04 13:52 -0700
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-15 13:19 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 18:17 +0100
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-15 19:07 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 21:46 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-16 01:41 +0000
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-15 22:37 -0400
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-16 03:30 +0000
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-15 20:50 -0700
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-16 18:11 +0000
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-16 18:43 +0000
Re: Loops (was Re: do { quit; } else { }) Richard Heathfield <rjh@cpax.org.uk> - 2025-04-16 20:05 +0100
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-02-03 03:47 -0800
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-02-03 04:21 -0800
Re: Loops (was Re: do { quit; } else { }) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-02-04 23:40 +0000
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-02-05 08:10 +0100
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2026-02-05 11:30 +0200
Re: Loops (was Re: do { quit; } else { }) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-02-05 15:21 +0000
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-16 14:12 +0000
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-16 07:35 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-16 12:32 +0100
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-16 15:08 +0300
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-16 14:23 +0000
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-04 21:32 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-16 15:31 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-18 15:01 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-18 15:34 +0100
Re: Loops (was Re: do { quit; } else { }) Alexis <flexibeast@gmail.com> - 2025-04-19 11:01 +1000
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-19 09:20 +0200
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-16 14:21 +0000
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-18 15:06 +0200
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-16 10:47 -0400
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-16 16:14 +0100
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-16 18:18 +0300
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-16 12:28 -0400
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-16 13:03 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-16 23:14 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-16 17:26 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-17 02:26 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-16 20:14 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-18 15:37 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-18 15:19 +0100
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-18 16:58 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-18 18:27 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-19 09:09 +0200
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-17 00:59 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-17 02:09 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-16 21:43 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-16 23:42 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-16 23:49 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-17 01:48 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-16 19:18 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-17 12:16 +0100
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-17 14:36 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-17 11:47 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-17 20:18 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-17 12:55 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-17 21:44 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-17 15:32 -0700
Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) gazelle@shell.xmission.com (Kenny McCormack) - 2025-04-17 21:21 +0000
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2025-04-17 22:29 +0000
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) gazelle@shell.xmission.com (Kenny McCormack) - 2025-04-18 13:58 +0000
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2025-04-18 18:33 +0000
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) bart <bc@freeuk.com> - 2025-04-18 20:10 +0100
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) bart <bc@freeuk.com> - 2025-04-18 16:07 +0100
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) scott@slp53.sl.home (Scott Lurndal) - 2025-04-18 16:52 +0000
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Rosario19 <Ros@invalid.invalid> - 2025-04-24 22:43 +0200
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-25 07:50 +0200
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Richard Harnden <richard.nospam@gmail.invalid> - 2025-04-25 07:04 +0100
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Rosario19 <Ros@invalid.invalid> - 2025-04-25 10:38 +0200
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Rosario19 <Ros@invalid.invalid> - 2025-04-25 10:42 +0200
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-18 15:24 +0000
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2025-04-18 15:48 +0000
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) bart <bc@freeuk.com> - 2025-04-18 16:57 +0100
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-18 18:46 +0200
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) bart <bc@freeuk.com> - 2025-04-18 18:40 +0100
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-19 08:36 +0200
Re: Checking the loop variable after the loop has ended (Was: Loops (was Re: do { quit; } else { })) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-18 17:49 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-17 02:19 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-16 17:47 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-18 14:41 +0200
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-16 14:09 +0000
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-16 17:37 +0300
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-06 05:59 -0700
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-05-07 12:32 +0300
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-07 14:54 +0200
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-05-07 13:50 +0000
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-11 23:48 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-16 15:45 +0100
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-16 15:44 +0000
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-16 13:18 -0700
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-15 19:55 +0000
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-16 07:19 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-16 07:44 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-16 12:01 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-18 16:40 +0200
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-18 14:10 -0400
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-18 23:27 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-19 08:27 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-19 11:26 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-19 13:32 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-19 14:05 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-19 12:54 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-19 20:57 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-19 14:07 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-20 00:34 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 12:18 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-20 12:43 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 18:46 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-20 20:51 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-20 15:36 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-21 00:29 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-20 19:08 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-21 12:26 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-21 03:16 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-21 12:57 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-21 18:43 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-21 20:57 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-21 20:25 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 00:33 +0100
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-21 23:46 +0000
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 10:32 +0200
Re: Loops (was Re: do { quit; } else { }) antispam@fricas.org (Waldek Hebisch) - 2025-04-22 01:06 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 02:24 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 10:47 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 11:28 +0100
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-22 19:19 +0200
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-22 19:26 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 21:03 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-22 21:40 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-23 00:43 +0100
Re: Loops (was Re: do { quit; } else { }) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-04-22 16:59 -0700
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-23 00:01 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-23 11:15 +0100
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-23 10:58 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-23 14:50 +0100
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-23 16:00 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-23 17:39 +0100
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-24 07:41 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-24 09:31 +0100
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-23 17:31 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-23 18:43 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-23 18:43 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-23 21:49 +0100
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-24 15:12 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-24 15:28 +0100
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-24 17:21 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-24 18:30 +0100
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-24 17:59 +0000
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-25 15:19 +0200
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-24 07:40 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-24 09:26 +0100
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-24 10:52 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-24 12:44 +0100
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-24 14:31 +0000
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-24 14:25 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-24 14:51 +0100
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-24 15:32 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-24 18:49 +0100
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-24 18:03 +0000
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-24 18:26 -0700
Re: Loops (was Re: do { quit; } else { }) Muttley@DastardlyHQ.org - 2025-04-25 08:53 +0000
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-04 22:17 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-09-26 02:00 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-25 02:56 +0000
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-25 13:48 +0200
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-25 17:51 +0200
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-25 17:48 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-24 18:51 +0200
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-23 09:01 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 09:32 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 09:14 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-20 15:07 -0700
Re: Loops (was Re: do { quit; } else { }) gazelle@shell.xmission.com (Kenny McCormack) - 2025-04-20 23:19 +0000
Re: Loops (was Re: do { quit; } else { }) antispam@fricas.org (Waldek Hebisch) - 2025-04-21 13:51 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-21 16:36 +0100
Re: Loops (was Re: do { quit; } else { }) antispam@fricas.org (Waldek Hebisch) - 2025-04-21 21:06 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-21 23:54 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-21 16:12 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 01:26 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-21 18:22 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 11:43 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-22 14:15 -0700
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 23:52 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-22 16:22 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 10:40 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-21 18:25 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 10:19 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 12:39 +0100
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 02:21 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 09:54 +0200
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-22 20:16 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 19:54 +0100
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-22 21:11 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 20:43 +0100
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-23 17:41 +0200
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-19 16:28 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-19 19:59 +0100
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-19 20:15 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 12:41 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 12:34 +0200
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-19 14:35 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-19 16:24 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-19 16:36 +0000
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-19 15:22 -0400
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-19 20:55 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-19 13:55 -0700
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-20 00:52 +0300
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 13:00 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-20 14:53 +0100
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-20 17:34 +0300
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-20 16:25 +0100
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-20 19:01 +0300
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 18:10 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 18:07 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 17:55 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-20 17:28 +0100
Re: Loops (was Re: do { quit; } else { }) antispam@fricas.org (Waldek Hebisch) - 2025-04-21 03:07 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-21 13:46 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-21 14:21 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 00:14 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 00:19 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-21 15:39 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-22 10:12 +0200
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-21 22:16 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 01:12 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-22 03:31 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 12:33 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-22 14:36 +0000
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-22 16:10 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-22 17:27 +0100
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-22 17:48 +0000
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-22 14:31 -0700
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-22 22:39 +0000
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-22 17:53 +0200
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-22 15:02 -0700
Re: Loops (was Re: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-23 19:05 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-23 18:52 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-23 13:22 -0700
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-21 07:34 -0400
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-21 13:26 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-21 13:39 -0700
Re: Loops (was Re: do { quit; } else { }) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-04 21:35 -0700
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-19 15:15 -0400
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-19 20:36 +0100
Re: Loops (was Re: do { quit; } else { }) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-04-19 19:43 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 11:27 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 11:25 +0200
Re: Loops (was Re: do { quit; } else { }) James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-20 11:25 -0400
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-20 16:53 +0100
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-16 12:29 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-16 12:38 +0100
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-16 19:15 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 15:28 +0100
Re: Loops (was Re: do { quit; } else { }) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-14 14:44 -0700
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-15 06:14 +0200
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-15 06:57 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-15 09:25 +0200
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-16 11:45 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-18 16:57 +0200
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-20 15:00 +0300
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-20 17:45 +0200
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-24 22:35 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-25 07:46 +0200
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-25 10:29 +0200
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-25 14:22 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 11:15 +0100
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-15 15:25 +0300
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 13:55 +0100
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-15 13:33 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 15:30 +0100
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-15 18:22 +0200
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 17:42 +0100
Re: Loops (was Re: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-15 20:14 +0300
Re: Loops (was Re: do { quit; } else { }) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-16 07:39 +0200
Re: Loops (was Re: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-15 20:37 +0000
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-16 12:09 +0200
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-16 12:04 +0200
Re: Loops (was Re: do { quit; } else { }) scott@slp53.sl.home (Scott Lurndal) - 2025-04-15 14:13 +0000
Re: Loops (was Re: do { quit; } else { }) bart <bc@freeuk.com> - 2025-04-15 15:41 +0100
Re: Loops (was Re: do { quit; } else { }) Rosario19 <Ros@invalid.invalid> - 2025-04-16 11:58 +0200
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-14 15:07 -0700
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-14 23:12 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-15 01:35 +0100
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-15 14:05 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-15 15:44 +0100
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-15 15:31 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-15 17:38 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-12 14:39 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-04-12 14:21 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-12 15:52 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-04-12 16:32 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-13 16:26 +0200
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-13 14:48 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-12 15:01 +0100
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-11 18:24 -0400
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-13 21:03 +0300
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-13 20:56 -0400
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 11:24 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-12 01:30 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-12 02:35 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-01-27 09:17 -0800
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-01-27 15:28 -0800
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 11:15 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-13 20:57 +0300
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-13 20:53 +0200
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-13 22:14 +0300
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-13 21:03 -0400
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-14 06:43 +0200
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-14 09:00 -0400
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-15 09:40 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-04-15 09:18 +0100
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-15 10:39 -0400
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-14 08:44 +0200
Re: do { quit; } else { } Ike Naar <ike@sdf.org> - 2025-04-11 19:45 +0000
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-11 16:00 -0400
Re: do { quit; } else { } antispam@fricas.org (Waldek Hebisch) - 2025-04-15 15:44 +0000
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-10 20:21 +0000
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 15:43 -0700
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-11 02:12 +0000
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 20:44 -0700
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-11 11:33 +0200
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-10 15:14 -0400
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-10 16:25 -0400
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-04-10 21:42 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-11 11:35 +0200
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-10 15:49 -0700
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-10 20:57 -0400
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-11 14:37 +0300
Re: do { quit; } else { } James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-04-11 11:16 -0400
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-11 18:31 +0300
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 11:10 -0700
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-11 14:02 +0000
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-04-11 15:24 +0000
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-11 18:46 +0300
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-04-11 12:01 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-08 10:47 -0700
Re: do { quit; } else { } Ike Naar <ike@sdf.org> - 2025-04-09 09:00 +0000
Re: do { quit; } else { } bart <bc@freeuk.com> - 2025-04-09 11:36 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-09 14:54 +0200
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-08 10:59 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-09 11:51 +0300
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-09 12:56 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-06 16:26 +0300
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-06 16:02 +0200
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-04-06 16:53 -0300
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 19:45 +0200
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-05-09 15:23 -0300
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-05-09 15:35 -0300
Re: do { quit; } else { } yeti <yeti@tilde.institute> - 2025-04-07 03:56 +0042
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-07 09:16 +0200
Re: do { quit; } else { } gazelle@shell.xmission.com (Kenny McCormack) - 2025-04-06 14:18 +0000
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-06 17:08 +0200
Beyond the pale... (Was: do { quit; } else { }) gazelle@shell.xmission.com (Kenny McCormack) - 2025-04-07 16:08 +0000
Re: Beyond the pale... (Was: do { quit; } else { }) David Brown <david.brown@hesbynett.no> - 2025-04-07 18:39 +0200
Re: Beyond the pale... (Was: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-07 23:30 +0000
Re: Beyond the pale... (Was: do { quit; } else { }) Michael S <already5chosen@yahoo.com> - 2025-04-08 12:39 +0300
Re: Beyond the pale... (Was: do { quit; } else { }) Kaz Kylheku <643-408-1753@kylheku.com> - 2025-04-08 16:57 +0000
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-07 08:06 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-06 08:14 -0700
Re: do { quit; } else { } Michael S <already5chosen@yahoo.com> - 2025-04-06 23:48 +0300
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-07 09:21 +0200
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-07 04:50 -0700
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 16:40 +0200
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-05-09 15:01 +0000
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 17:04 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 16:26 +0100
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-09 17:54 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 17:26 +0100
Re: do { quit; } else { } scott@slp53.sl.home (Scott Lurndal) - 2025-05-09 17:07 +0000
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 19:11 +0100
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 20:21 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 19:35 +0100
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 19:09 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 19:29 +0100
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-13 14:55 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-13 14:35 +0100
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-14 11:22 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 10:34 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-09 19:09 +0200
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 19:11 +0200
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-09 19:18 +0200
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-13 14:54 +0200
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-13 15:36 +0200
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-14 11:19 +0200
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-12 11:44 -0700
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-13 15:13 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-13 14:46 +0100
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-05-13 16:07 +0200
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-13 14:05 -0700
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-05-14 11:31 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 10:37 +0100
Re: do { quit; } else { } Kaz Kylheku <643-408-1753@kylheku.com> - 2025-05-09 15:31 +0000
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 19:07 +0200
Re: do { quit; } else { } Wuns Haerst <Wuns.Haerst@wurstfabrik.at> - 2025-05-07 06:56 +0200
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 06:52 +0100
Re: do { quit; } else { } Wuns Haerst <Wuns.Haerst@wurstfabrik.at> - 2025-05-07 15:46 +0200
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-08 06:04 -0700
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 14:24 -0700
Re: do { quit; } else { } Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-01-27 09:15 -0800
Re: do { quit; } else { } Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-01-27 15:36 -0800
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-09 11:09 +0200
Re: do { quit; } else { } Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-06 02:58 +0000
Re: do { quit; } else { } David Brown <david.brown@hesbynett.no> - 2025-04-06 12:05 +0200
Re: do { quit; } else { } Mikko <mikko.levanto@iki.fi> - 2025-04-18 10:30 +0300
Re: do { quit; } else { } Anton Shepelev <anton.txt@g{oogle}mail.com> - 2025-10-08 14:14 +0300
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-10-08 09:59 -0300
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-10-08 16:05 +0200
Re: do { quit; } else { } Anton Shepelev <anton.txt@g{oogle}mail.com> - 2025-10-08 17:08 +0300
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-10-08 16:35 +0200
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-10-15 16:04 -0300
Re: do { quit; } else { } Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-10-08 16:06 +0200
Re: do { quit; } else { } Bonita Montero <Bonita.Montero@gmail.com> - 2025-10-15 23:04 +0200
Re: do { quit; } else { } Thiago Adams <thiago.adams@gmail.com> - 2025-10-15 20:41 -0300
Re: do { quit; } else { } Richard Heathfield <rjh@cpax.org.uk> - 2025-10-16 00:43 +0100
Page 6 of 35 — ← Prev page 1 … 4 5 [6] 7 8 … 35 Next page →
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2025-05-04 22:01 -0700 |
| Message-ID | <86h61z6489.fsf@linuxsc.com> |
| In reply to | #392365 |
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes: > Tim Rentsch <tr.17687@z991.linuxsc.com> writes: > >> Keith Thompson <Keith.S.Thompson+u@gmail.com> writes: >> >>> Tim Rentsch <tr.17687@z991.linuxsc.com> writes: > > [...] > >>>> I withdraw my earlier statement. Please leave me out of any >>>> future discussion of the subject. >>> >>> Do you mean that your earlier statement was incorrect (i.e., that >>> the types are compatible), or do you merely wish to pretend you >>> never said anything without taking a position on whether they're >>> compatible, or do you refuse to say? >> >> I am specifically _not_ saying either that my earlier statement >> was right or that my earlier statement was wrong. My hope is >> that henceforth people will act as though the statement never >> entered the discussion. Does that clarify the matter for you? > > That answers precisely what I was asking, thank you. > > As often happens, I am mystified by your decision, but it is > unquestionably yours. I'm sorry. I didn't mean it to be mystifying; just the opposite. > I'll try not to include you in any further discussion, but I do > not promise to try very hard. For reference my request to leave me out of any future discussion of the subject was meant primarily for the person to whose post I was responding. But thank you for your effort.
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2025-04-10 21:20 -0700 |
| Message-ID | <87jz7rtjlq.fsf@nosuchdomain.example.com> |
| In reply to | #392329 |
bart <bc@freeuk.com> writes:
> On 10/04/2025 17:51, Kaz Kylheku wrote:
>> On 2025-04-10, bart <bc@freeuk.com> wrote:
>
>>> Do you agree with that? Or is there something more to making two types
>>> be incompatible?
>> Tim: two fingerprints from the left hand index finger are from
>> different
>> humans if they are different.
>> You: do you agree with this, or is there more that can make
>> two humans different?
>> Struct compatibility is determined by tag and content.
>
> This is more nuanced. There is two structs being the same type or not,
> which a compiler can determine if they are in the same translation
> unit; no need to analyse tags or anything to figure that out, it's
> either the exact same type or not.
>
> And there is two structs in two translation units which have separate
> definitions, which the compiler cannot compare, and which have to be
> compatible for the program to be valid. But the compiler cannot check
> that.
>
> The example was like this:
>
> module A: typedef struct point {float a; float b;} Point;
>
> module B: typedef float length;
> typedef struct _tag {length x, y;} vector;
I know I said I didn't care about the specific types, but now that I've
seen a concise example (via a followup someone else posted), I've
decided to take a look. I'm allowed to change my mind.
I'll assume that "module A" and "module B" mean that the two
declarations are in different translation units. I'll assume that
the declarations are *exactly* like the above. I won't assume
anything about whether the above example accurately reflects the
types that were discussed earlier.
My reading of the standard is that the two types are clearly *not*
compatible. (Irrelevantly, they're very likely to have the same
representation.)
I'll refer to the N3096 draft of C23, section 6.2.7. I don't think
other editions give different answers.
Two complete struct types *with the same tag* are compatible if
they meet certain requirements. These types have different tags,
"point" and "_tag", so those requirements are irrelevant here.
Furthermore, two structure, union, or enumerated types declared in
separate translation units are compatible in the following cases:
- both are declared without tags and they fulfill the requirements
above;
— both have the same tag and are completed somewhere in their
respective translation units and they fulfill the requirements above;
— both have the same tag and at least one of the two types is not
completed in its translation unit.
None of these three bullet points applies to types with different tags
*or* to types with different member names (a, b vs. x, y).
Otherwise, the structure, union, or enumerated types are
incompatible.
Conclusion: They're incompatible.
Two regular users commented on *some* pair of types and disagreed
on whether they're compatible. I won't comment here on who was
correct, because I don't know whether they were talking about the
types quoted above.
[...]
Practically, if you need two translation units to use compatible struct
types, you should define the type in a shared header. That guarantees
(assuming no nasty tricks are played before the #include directive) that
the types have the same tag, and the same member names and types in the
same order.
--
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 | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2025-04-10 21:22 -0700 |
| Message-ID | <87iknbtjib.fsf@nosuchdomain.example.com> |
| In reply to | #392329 |
bart <bc@freeuk.com> writes:
> On 10/04/2025 17:51, Kaz Kylheku wrote:
>> On 2025-04-10, bart <bc@freeuk.com> wrote:
>
>>> Do you agree with that? Or is there something more to making two types
>>> be incompatible?
>> Tim: two fingerprints from the left hand index finger are from
>> different
>> humans if they are different.
>> You: do you agree with this, or is there more that can make
>> two humans different?
>> Struct compatibility is determined by tag and content.
>
> This is more nuanced. There is two structs being the same type or not,
> which a compiler can determine if they are in the same translation
> unit; no need to analyse tags or anything to figure that out, it's
> either the exact same type or not.
>
> And there is two structs in two translation units which have separate
> definitions, which the compiler cannot compare, and which have to be
> compatible for the program to be valid. But the compiler cannot check
> that.
>
> The example was like this:
>
> module A: typedef struct point {float a; float b;} Point;
>
> module B: typedef float length;
> typedef struct _tag {length x, y;} vector;
I know I said I didn't care about the specific types, but now that I've
seen a concise example (via a followup someone else posted), I've
decided to take a look. I'm allowed to change my mind.
I'll assume that "module A" and "module B" mean that the two
declarations are in different translation units. I'll assume that
the declarations are *exactly* like the above. I won't assume
anything about whether the above example accurately reflects the
types that were discussed earlier.
My reading of the standard is that the two types are clearly *not*
compatible. (Irrelevantly, they're very likely to have the same
representation.)
I'll refer to the N3096 draft of C23, section 6.2.7. I don't think
other editions give different answers.
Two complete struct types *with the same tag* are compatible if
they meet certain requirements. These types have different tags,
"point" and "_tag", so those requirements are irrelevant here.
Furthermore, two structure, union, or enumerated types declared in
separate translation units are compatible in the following cases:
- both are declared without tags and they fulfill the requirements
above;
— both have the same tag and are completed somewhere in their
respective translation units and they fulfill the requirements above;
— both have the same tag and at least one of the two types is not
completed in its translation unit.
None of these three bullet points applies to types with different tags
*or* to types with different member names (a, b vs. x, y).
Otherwise, the structure, union, or enumerated types are
incompatible.
Conclusion: They're incompatible.
Two regular users commented on *some* pair of types and disagreed
on whether they're compatible. I won't comment here on who was
correct, because I don't know whether they were talking about the
types quoted above.
[...]
Practically, if you need two translation units to use compatible struct
types, you should define the type in a shared header. That guarantees
(assuming no nasty tricks are played before the #include directive) that
the types have the same tag, and the same member names and types in the
same order.
--
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 | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2025-04-10 21:24 -0700 |
| Message-ID | <87ecxztjeo.fsf@nosuchdomain.example.com> |
| In reply to | #392362 |
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
[...]
> I know I said I didn't care about the specific types, but now that I've
[...]
Apologies for the double posting. Both articles are identical. Please
ignore one or both of them.
--
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 | 2025-04-10 20:11 +0100 |
| Message-ID | <vt9544$3hhr8$2@dont-email.me> |
| In reply to | #392327 |
On 10/04/2025 17:51, Kaz Kylheku wrote:
> On 2025-04-10, bart <bc@freeuk.com> wrote:
>> In my C compiler, each type has a unique index which is what is compared
>> to see if two types are the same type. It has nothing to do with tags.
>
> How can it not?
>
> struct tag;
> struct tag { ... };
>
> these have to refer to the same type; how do you do that without tags?
The type can be denoted in the source code using 'struct tag'. Looking
'tag' up in the ST, checking only names belonging to the special tag
namespace, will yield an entry that has its type index, whatever that
happens to be.
But the tag is not what is used when comparing two types. It is just an
anachronistic concept that C still needs.
(In C++ I understand that special tag namespaces don't exist, they are
just part of the normal namespace.
And in my languages they have never been a concept, yet I can still
compare one struct type with another.)
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2025-04-11 10:07 -0700 |
| Message-ID | <86r01yaaoj.fsf@linuxsc.com> |
| In reply to | #392299 |
bart <bc@freeuk.com> writes: > On 09/04/2025 23:07, Tim Rentsch wrote: > >> bart <bc@freeuk.com> writes: >> >>> On 09/04/2025 00:27, Tim Rentsch wrote: >>> >>>> bart <bc@freeuk.com> writes: >>>> >>>>>> If you want to make a point or ask a question about C code, >>>>>> SHOW THE CODE. And show all of it. Don't make people guess by >>>>>> showing only some of the code or by giving just a description. >>>>> >>>>> I'm showing the code but you keep snipping it! [...] >>>> >>>> No, I don't. Don't be so obtuse. I included the code I was >>>> originally commenting on, in my first followup. My comment about >>>> showing code was about your second posting. Let me repeat the >>>> two important paragraphs (quoted above) taken from that posting: >>>> >>>>>>> I get an incompatible error (from the example you snipped) >>>>>>> even when I remove both struct tags. >>>> >>>> The phrase "even when I remove both struct tags" describes code, it >>>> doesn't show the code. >>> >>> I showed this example a few lines later [in an earlier posting] >>> which has both struct tags omitted: >> >> There is a simple lesson that you need to learn: > > Please don't be patronising. We are not kids in your PL class. I'm sorry you feel that way. I was trying to be helpful.
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2025-05-09 16:25 +0200 |
| Message-ID | <vvl38r$2rktk$1@raubtier-asyl.eternal-september.org> |
| In reply to | #392295 |
Am 10.04.2025 um 00:07 schrieb Tim Rentsch: > When someone is responding to a post, they are responding ONLY to > the content in the posting they are responing to; not to some > earlier posting in the same thread, not to a different posting > submitted two weeks ago, not to what you meant to say but didn't, > not to thoughts in your head but that you didn't say, but ONLY TO > WHAT IS SAID IN THE POSTING BEING RESPONDED TO. > > If you can learn to follow this simple rule everyone in the > newsgroup will be better off, including you. You're constantly overwhelmed by what people write here. Both in terms of content and the nature of the discussion. Don't try to constantly set rules; that seems petty.
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2025-05-09 15:38 +0100 |
| Message-ID | <vvl422$2q824$2@dont-email.me> |
| In reply to | #393287 |
On 09/05/2025 15:25, Bonita Montero wrote: > Am 10.04.2025 um 00:07 schrieb Tim Rentsch: > >> When someone is responding to a post, they are responding ONLY to >> the content in the posting they are responing to; not to some >> earlier posting in the same thread, not to a different posting >> submitted two weeks ago, not to what you meant to say but didn't, >> not to thoughts in your head but that you didn't say, but ONLY TO >> WHAT IS SAID IN THE POSTING BEING RESPONDED TO. >> >> If you can learn to follow this simple rule everyone in the >> newsgroup will be better off, including you. > > You're constantly overwhelmed by what people write here. Both in > terms of content and the nature of the discussion. Don't try to > constantly set rules; that seems petty. Tim's not setting a draconian rule in stone. He's presenting a perfectly sensible rule of thumb that is based on his decades of experience of posting to this group. Usenet works best when you snip the bits you're not replying to, and reply only within the context you have retained. Nearly all the leading experts in this group nearly always observe this rule of thumb, because it's simple common sense so to do. On what basis do you justify laying down your law for Tim to follow? -- Richard Heathfield Email: rjh at cpax dot org dot uk "Usenet is a strange place" - dmr 29 July 1999 Sig line 4 vacant - apply within
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2025-05-09 16:42 +0200 |
| Message-ID | <vvl496$2rt1b$2@raubtier-asyl.eternal-september.org> |
| In reply to | #393288 |
Am 09.05.2025 um 16:38 schrieb Richard Heathfield: > Tim's not setting a draconian rule in stone. He's presenting a perfectly > sensible rule of thumb that is based on his decades of experience of > posting to this group. ... No, he's just annoyed. It is perfectly normal to go from one topic to another in such a deep thread
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2025-05-09 17:43 +0200 |
| Message-ID | <vvl7qv$2spjf$1@dont-email.me> |
| In reply to | #393290 |
On 09/05/2025 16:42, Bonita Montero wrote: > Am 09.05.2025 um 16:38 schrieb Richard Heathfield: > >> Tim's not setting a draconian rule in stone. He's presenting a >> perfectly sensible rule of thumb that is based on his decades of >> experience of posting to this group. ... > > No, he's just annoyed. It is perfectly normal to > go from one topic to another in such a deep thread He was not annoyed at people jumping topics. (Well, he might well have been annoyed at that too - I don't claim to know Tim's mind, just his posts.) He was frustrated by another poster making comments that referred to details in another post. Occasionally that might make sense, to avoid repetition, but often it fragments the conversation and makes it hard for people to know what the poster is talking about. Thus Tim's suggestion is generally a good rule, but as Richard says, it is not set in stone, and of course Tim is perfectly aware that he can write rules, but has no authority to enforce them. I posted a rule of my own recently - do not reply to posts that are over a week old in dead threads unless you have something very significant or interesting to say. I hope you learn to follow that one too.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2025-05-13 19:34 -0700 |
| Message-ID | <86a57fx6n0.fsf@linuxsc.com> |
| In reply to | #393288 |
Richard Heathfield <rjh@cpax.org.uk> writes: > On 09/05/2025 15:25, Bonita Montero wrote: > >> Am 10.04.2025 um 00:07 schrieb Tim Rentsch: >> >>> When someone is responding to a post, they are responding ONLY to >>> the content in the posting they are responing to; not to some >>> earlier posting in the same thread, not to a different posting >>> submitted two weeks ago, not to what you meant to say but didn't, >>> not to thoughts in your head but that you didn't say, but ONLY TO >>> WHAT IS SAID IN THE POSTING BEING RESPONDED TO. >>> >>> If you can learn to follow this simple rule everyone in the >>> newsgroup will be better off, including you. >> >> You're constantly overwhelmed by what people write here. Both in >> terms of content and the nature of the discussion. Don't try to >> constantly set rules; that seems petty. > > Tim's not setting a draconian rule in stone. He's presenting a > perfectly sensible rule of thumb that is based on his decades of > experience of posting to this group. Usenet works best when you snip > the bits you're not replying to, and reply only within the context you > have retained. Nearly all the leading experts in this group nearly > always observe this rule of thumb, because it's simple common sense so > to do. Note that my remarks did not direct anyone to do anything. The first paragraph gives an observation -- which I think agrees with the behavior of most posters in most cases -- about how responders actually act. The second paragraph gives a statement of opinion (or perhaps a prediction, depending on how the paragraph is interpreted) about what will happen if someone adopts the view explained in the first paragraph. There was no attempt to set rules. > On what basis do you justify laying down your law for Tim to follow? I see no reason to care what Bonita Montero thinks. ISTM that the most common reaction among other responders is to say postings not topical to comp.lang.c should be posted elsewhere. So I don't think there is much danger of my reaction being in the minority.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <richard@damon-family.org> |
|---|---|
| Date | 2025-04-09 07:15 -0400 |
| Message-ID | <3d87646ba474317aea665fa213e7f78bb5f4f437@i2pn2.org> |
| In reply to | #392211 |
On 4/8/25 2:04 PM, bart wrote:
> On 08/04/2025 18:32, Tim Rentsch wrote:
>> bart <bc@freeuk.com> writes:
>>
>>> On 08/04/2025 15:50, David Brown wrote:
>>>
>>>> On 08/04/2025 13:35, bart wrote:
>>>>
>>>>> But this need not be the case. For example this is module A:
>>>>>
>>>>> --------------------------
>>>>> #include <stdio.h>
>>>>>
>>>>> typedef struct point {float a; float b;} Point;
>>>>>
>>>>> float dist(Point);
>>>>>
>>>>> int main(void) {
>>>>> Point p = {3, 4};
>>>>> printf("%f\n", dist(p));
>>>>> }
>>>>> --------------------------
>>>>>
>>>>> And this is module B that defines 'dist':
>>>>>
>>>>>
>>>>> --------------------------
>>>>> #include <math.h>
>>>>>
>>>>> typedef float length;
>>>>> typedef struct _tag {length x, y;} vector;
>>>>>
>>>>> length dist(vector p) {return sqrt(p.x*p.x + p.y*p.y);}
>>>>> --------------------------
>>>>>
>>>>> The types involved are somewhat different, but are compatible
>>>>> enough for it to work.
>>>>
>>>> The two types are entirely compatible.
>>>
>>> Are they?
>>
>> No, they are not. The type names 'Point' and 'vector' name two
>> distinct types, and those types are not compatible, because
>> the two struct tags are different.
>>
>> Because the two types are not compatible, even just calling the
>> function dist() is undefined behavior.
>
> I get an incompatible error (from the example you snipped) even when I
> remove both struct tags.
>
> I can't use the same struct tag in the same scope as one will clash with
> the other. But if I have the second in an inner scope, then I again get
> the error.
>
> It doesn't seem to be anything to do with struct tags.
>
> Two typedefs for same struct layout appear to create distinct types;
> this fails:
>
> typedef struct {float x, y;} Point;
> typedef struct {float x, y;} vector;
>
> Point p;
> vector v;
>
> p=v;
>
>
> But this works:
>
> typedef struct {float x, y;} Point, vector;
>
> Point p;
> vector v;
>
> p=v;
>
> So it seems to depend on whether Point and vector share the same
> internal descriptor for the struct.
>
> In my original example, the structs were defined in separate translation
> unit, so the compiler has to take things on trust.
>
I think the key point is that every time you define a struct with the
struct keyword, it gets a "tag", if you don't provide it, it gets a
private unnamable one, that is distinct. Thus you can't define a struct
twice and get the exact same type, so every occurance of
struct { float x, y; };
will create a new type, so you can't use one in the place of another.
The "Names" of types in C don't cross transition unit boundries, and it
has a rule that two structs, with the same component by component
definitions in two different translation units are compatible.
So, in one C file you could have:
typedef struct {float x, y; } Point;
void fun(Point* p) { .... }
and in another C file you could have:
typedef struct { float x, y; } Vector;
extern fun(Vector* v);
Vector v;
...
fun(&v);
and have fully defined behavior, as the names of the type don't matter
in C, just the memory layout.
WITHIN a translation unit, you can't do that as names of types DO matter
within a single translation unit,
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2025-04-09 13:51 +0200 |
| Message-ID | <vt5n0s$inuo$1@dont-email.me> |
| In reply to | #392211 |
On 08/04/2025 20:04, bart wrote:
> On 08/04/2025 18:32, Tim Rentsch wrote:
>> bart <bc@freeuk.com> writes:
>>
>>> On 08/04/2025 15:50, David Brown wrote:
>>>
>>>> On 08/04/2025 13:35, bart wrote:
>>>>
>>>>> But this need not be the case. For example this is module A:
>>>>>
>>>>> --------------------------
>>>>> #include <stdio.h>
>>>>>
>>>>> typedef struct point {float a; float b;} Point;
>>>>>
>>>>> float dist(Point);
>>>>>
>>>>> int main(void) {
>>>>> Point p = {3, 4};
>>>>> printf("%f\n", dist(p));
>>>>> }
>>>>> --------------------------
>>>>>
>>>>> And this is module B that defines 'dist':
>>>>>
>>>>>
>>>>> --------------------------
>>>>> #include <math.h>
>>>>>
>>>>> typedef float length;
>>>>> typedef struct _tag {length x, y;} vector;
>>>>>
>>>>> length dist(vector p) {return sqrt(p.x*p.x + p.y*p.y);}
>>>>> --------------------------
>>>>>
>>>>> The types involved are somewhat different, but are compatible
>>>>> enough for it to work.
>>>>
>>>> The two types are entirely compatible.
>>>
>>> Are they?
>>
>> No, they are not. The type names 'Point' and 'vector' name two
>> distinct types, and those types are not compatible, because
>> the two struct tags are different.
>>
>> Because the two types are not compatible, even just calling the
>> function dist() is undefined behavior.
>
> I get an incompatible error (from the example you snipped) even when I
> remove both struct tags.
Of course. They are different types.
>
> I can't use the same struct tag in the same scope as one will clash with
> the other.
Yes.
> But if I have the second in an inner scope, then I again get
> the error.
Yes.
>
> It doesn't seem to be anything to do with struct tags.
Correct.
Every time you declare a struct - when you have "struct {" or "struct X
{", you declare a /new/ type that is incompatible with any other type
(except for inter-translation unit compatibility).
>
> Two typedefs for same struct layout appear to create distinct types;
> this fails:
"typedef" does not create types - it merely creates an alias for an
existing type. (Is it a questionable choice of keyword? Yes, it
certainly is. So you have to learn what it means.) "struct"
declarations (and "union" declarations) create types.
>
> typedef struct {float x, y;} Point;
This creates a new anonymous type, then declares "Point" to be an alias
for it.
> typedef struct {float x, y;} vector;
This creates a new anonymous type, then declares "vector" to be an alias
for it.
"Point" and "vector" thus refer to different types.
>
> Point p;
> vector v;
>
> p=v;
>
>
> But this works:
>
> typedef struct {float x, y;} Point, vector;
This creates a new anonymous type, then declares "Point" and "vector" to
be aliases of it. They therefore refer to the same type.
>
> Point p;
> vector v;
>
> p=v;
>
> So it seems to depend on whether Point and vector share the same
> internal descriptor for the struct.
>
It depends on whether they are declared as aliases for the same type, or
for different types.
> In my original example, the structs were defined in separate translation
> unit, so the compiler has to take things on trust.
>
Yes - as explained in 6.2.7p1 of the standard. Having them in separate
translation units is critical to the difference.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2025-04-09 11:42 +0200 |
| Message-ID | <vt5fed$ccri$1@dont-email.me> |
| In reply to | #392203 |
On 08/04/2025 18:28, bart wrote:
> On 08/04/2025 15:50, David Brown wrote:
>> On 08/04/2025 13:35, bart wrote:
>
>>> But this need not be the case. For example this is module A:
>>>
>>> --------------------------
>>> #include <stdio.h>
>>>
>>> typedef struct point {float a; float b;} Point;
>>>
>>> float dist(Point);
>>>
>>> int main(void) {
>>> Point p = {3, 4};
>>> printf("%f\n", dist(p));
>>> }
>>> --------------------------
>>>
>>> And this is module B that defines 'dist':
>>>
>>>
>>> --------------------------
>>> #include <math.h>
>>>
>>> typedef float length;
>>> typedef struct _tag {length x, y;} vector;
>>>
>>> length dist(vector p) {return sqrt(p.x*p.x + p.y*p.y);}
>>> --------------------------
>>>
>>> The types involved are somewhat different, but are compatible enough
>>> for it to work.
>>
>> The two types are entirely compatible.
>
>
> Are they?
Yes.
> So why does gcc report an error here (the two types are from
> my example):
>
> typedef struct point {float a; float b;} Point;
>
> typedef float length;
> typedef struct _tag {length x, y;} vector;
>
> Point p;
> vector v;
>
> p=v;
>
> c.c:14:5: error: incompatible types when assigning to type 'Point' {aka
> 'struct point'} from type
> ector' {aka 'struct _tag'}
> 14 | p=v;
> | ^
>
That is a different situation. In the first case, the types were
defined in different translation units - and are compatible. In the
second case, they are within the same translation unit, and are not
compatible.
In C, if you declare two structs in the same translation unit with the
same field types and the same field names, they are still different
types. That is important for making new types - it is how you get
strong typing in C (albeit with less user convenience than in some other
languages). It means that you can't mix up two types just because of
coincidences in the fields.
This means that when you have a struct declaration in two translation
units (locally in the C file, or via a header file - there is no
distinction), they form two different types as they are separate
declarations. If C did not specify that these were compatible, it would
be impossible (without UB) to use struct or union types across
translation units.
This is a situation where C's system is weaker than a solid module
solution, but it works extremely well in practice - especially if
developers follow the simple and common habit of putting shared type
declarations in shared header files.
>
>> "typedef" does not introduce a new type, and struct types in different
>> modules are compatible if they are build from the same compatible
>> field types in the same order.
>>
>>>
>>> However, they could also be different enough (in a more elaborate
>>> example) for things to superficially work.
>>
>> Not in C.
>
> Really? I could have added a dozen extra fields to one (or a pile of
> incompatible fields to both), and it can still work (especially if I
> pass the struct by reference).
The fact that something happens to work does not mean that it is defined
behaviour in C.
Of course it can be appropriate to write non-portable code that "just
works". Making a pointer to one struct type, then using it as though it
is a pointer to a different struct type like this is very likely to
"just work" as long as you stay within the common part of the struct
types. But there also may be circumstances in which it does /not/ "just
work", or it might not work with other compilers or other options.
>
>>> The preprocessor mechanisms available to work with source code are
>>> fairly easy to grasp (but may be complex in practice with multiple
>>> nested headers spread over a file system).
>
>> That's like complaining that integer addition is complex because
>> someone might want to add 26 digit numbers. Stop being silly.
>
> You're missing the point: the concept may be simple, but as typically
> used in C, it is can be much more complex than necessary.
The C language is defined as explained in the standards. If someone
writes C code that you think is more complex than necessary, talk to the
person writing that code.
> Doing:
>
> #include "lib.h"
>
> is not enough; there may be a dozen different header locations (from
> nested includes) that need to be made known to the compiler, so you need
> to figure them out first!
That is a question of build environment and build instructions. It
applies to every programming language. Any time one file refers to
another, you need some way to be sure you get exactly the file you intended.
>
> A program may comprise 100 .c files, but use 37 different headers in
> mixed, possible nested combinations across those 100 modules. You can't
> in general tie one .c file to a specific .h file; /that/ would be simpler.
>
This applies to all languages. For example, in Python you do not have
separate "interface" and "implementation" files - everything is in one
".py" file. If I have a Python module that says "import my_py_lib", how
does Python know where to find "my_py_lib.py" ? How does it know which
copy of "my_py_lib.py" to use from the dozen that I have on my computer?
The answer is it uses some default rules for the language, some
default rules for the implementation, some configuration settings, some
flags, some run-time information (equivalent to compile-time information
in compiled languages). The exact details are different, but the
principle is the same for C and for any other language that can handle
more than one file.
> So the usual thing applies in C: the language lays down some vague
> rules, beyond that it's a free-for-all.
>
> You choose to call that 'being flexible'; I might call it something else.
>
>>
>>>
>>> But I had, and do still have, difficulty with how exactly you import
>>> and export entities, even ones with linkage.
>>
>> That sounds very much like a "Bart" problem.
>
> You really think that I wouldn't know how to do this if the language
> provided genuinely simple and well-thought-out and consistent rules?
Apparently, that is the case. It does surprise me a little that you
find this difficult - especially since you claim to have written a C
compiler but don't seem to have read any of the language standards.
>
>
>> If you /genuinely/ want to know, and you can't figure it out with a
>> quick google search, reading the page in the standards, or looking at
>> an introduction to C book, then please ask. If you are just trying to
>> claim opportunities to say it's all so difficult and confusing, then
>> don't bother.
>
> Ah yes, the Microsoft approach: provide huge amounts of resources,
> manuals, training courses etc, rather than making something actually
> simple!
It is /one/ **beeping** page in the standard! It is in /one/ section -
section 6.2.2 - titled "Linkages of identifiers". Seven paragraphs,
none of which are more than 5 lines long.
>
>>>
>>> How compilers deal with it have changed.
>>
>> As a general rule, they have not.
>>
>> But it is true that some compilers have by default supported an
>> extension that was designed to make interoperability with Fortran
>> programs easier
>
> Which means a pile of badly written programs.
That is why I said it was a bad idea for gcc to have "-fcommon" as the
default. It is a real shame that it took so long to change it.
However, while that default meant that some people wrote C code with a
misunderstanding of linkages and the difference between declarations and
definitions, most C programmers don't make that mistake. When gcc
eventually changed the default, it did not lead to wide-spread breakage
of code.
>
>>> However if I need to initialise the variable:
>>>
>>> extern int table[]; // shared
>>> int table[] = (10, 20, 30)
>>>
>>> then other modules can't pick up length of the array.
>>>
>>
>> Correct.
>
> And the workaround is...?
Learn how arrays work in C, and how you can pass around the length of an
array between different functions or translation units.
>
> (Maybe you can appreciate one of many reasons why I normally generate C
> code for a project as one source file.)
I can appreciate that you are the sort of person who, when finding a
hole in their sock, would rather chop off their foot than go to the
effort of buying a new pair.
No one claims that C is the ideal language for all programming tasks or
all programmers - if you would rather use a different language, that's
fine. It's the petty griping and whining about things that are simple
and clear that is so pathetic. You /know/ that C does not pass on the
array size in the case you give above. You /know/ you have not shared
that information with the second unit. You /know/ that no language lets
one unit or module know information from a different unit or module if
that information is not shared. And you know perfectly well how you can
pass around the information in C when you need to.
>
>> The C standard gives clear rules here that make sense.
>
> What's the rational for allowing both static and extern versions of the
> same entity in the same file? And if that is allowed, why does the order
> matter?
I believe the meaning of "extern" in combination with other
storage-class specifiers was picked to work with existing old code from
before "extern" was added to the language.
(You might not think this is a good reason, or prefer the rules to be
different - that's fine. I would certainly prefer stricter rules, and
use compiler warnings to enforce those preferences in order to reduce
the risk of errors in my code.)
>
> (In my compiler I gave up trying to make sense of it, and just ended up
> allow any combination unless it was clearly wrong.)
Again, it is /one/ page in the standard. It is not rocket science. The
idea that a person could be smart enough to make their own compiler and
not smart enough to understand the rules around linkage in C is utterly
laughable. You have are intentionally misunderstanding this so that you
can claim C is confusing or badly designed. This is deceitful behaviour.
No one is asking you to /like/ the rules of C. No one is asking you to
think they are ideal. Certainly no C programmer I know likes all of C's
design, though they vary on what they like and dislike. But you are
clearly wrong about these things being hard to understand.
>
> That does not
>> mean they are the /only/ set of rules a language could have that makes
>> sense, but they are not "ad hoc". That would imply that combinations
>> like this could have unpredictable meanings.
>
> I don't mean 'ad hoc' to be 'indeterminate'. More like, 'mess', or
> 'free-for-all'.
>
You are still wrong.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2025-04-09 13:04 +0300 |
| Message-ID | <20250409130449.00002f85@yahoo.com> |
| In reply to | #392246 |
On Wed, 9 Apr 2025 11:42:36 +0200 David Brown <david.brown@hesbynett.no> wrote: > > In C, if you declare two structs in the same translation unit with > the same field types and the same field names, they are still > different types. That is clear for structs with tags. Less clear for tagless structs that have exactly the same fields.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2025-04-09 14:06 +0200 |
| Message-ID | <vt5nsl$inuo$2@dont-email.me> |
| In reply to | #392248 |
On 09/04/2025 12:04, Michael S wrote: > On Wed, 9 Apr 2025 11:42:36 +0200 > David Brown <david.brown@hesbynett.no> wrote: > >> >> In C, if you declare two structs in the same translation unit with >> the same field types and the same field names, they are still >> different types. > > That is clear for structs with tags. Less clear for tagless structs > that have exactly the same fields. > (Note - I am referencing C11 here for personal convenience, but the section numbering and contents is, AFAIR, the same from C99 up to C17. C23 changed the numbering a bit.) 6.7.2.1 "Structure and union specifiers" paragraph 8: """ The presence of a struct-declaration-list in a struct-or-union-specifier declares a new type, within a translation unit. """ So two tagless structs with the same fields declared, compatibility is the same as always - within a translation unit, they declare distinct incompatible new types, while across translation units they are compatible. 6.2.7 "Compatible type and composite type" paragraph 1: """ Two types have compatible type if their types are the same. Additional rules for determining whether two types are compatible are described in 6.7.2 for type specifiers, in 6.7.3 for type qualifiers, and in 6.7.6 for declarators. 55) Moreover, two structure, union, or enumerated types declared in separate translation units are compatible if their tags and members satisfy the following requirements: If one is declared with a tag, the other shall be declared with the same tag. If both are completed anywhere within their respective translation units, then the following additional requirements apply: there shall be a one-to-one correspondence between their members such that each pair of corresponding members are declared with compatible types; """
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@alumni.caltech.edu> |
|---|---|
| Date | 2025-04-11 12:27 -0400 |
| Message-ID | <vtbfsn$1tc7o$3@dont-email.me> |
| In reply to | #392248 |
On 4/9/25 06:04, Michael S wrote: > On Wed, 9 Apr 2025 11:42:36 +0200 > David Brown <david.brown@hesbynett.no> wrote: > >> >> In C, if you declare two structs in the same translation unit with >> the same field types and the same field names, they are still >> different types. > > That is clear for structs with tags. Less clear for tagless structs > that have exactly the same fields. "Two declarations of structure, union, or enumerated types which are in different scopes or use different tags declare distinct types. Each declaration of a structure, union, or enumerated type which does not include a tag declares a distinct type." (6.7.2.3p9)
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2025-04-09 13:11 +0300 |
| Message-ID | <20250409131124.00006e26@yahoo.com> |
| In reply to | #392246 |
On Wed, 9 Apr 2025 11:42:36 +0200 David Brown <david.brown@hesbynett.no> wrote: > > This applies to all languages. For example, in Python you do not > have separate "interface" and "implementation" files - everything is > in one ".py" file. If I have a Python module that says "import > my_py_lib", how does Python know where to find "my_py_lib.py" ? How > does it know which copy of "my_py_lib.py" to use from the dozen that > I have on my computer? The answer is it uses some default rules for > the language, some default rules for the implementation, some > configuration settings, some flags, some run-time information > (equivalent to compile-time information in compiled languages). The > exact details are different, but the principle is the same for C and > for any other language that can handle more than one file. > It is not quite the same for all languages. The degree in which it is standardizes vs left to implementation differs. In some languages it is fully standardized. I think, in case of Ada it was standardized in APSE. But then, real world mostly accepted a language part of Ada standard and mostly ignored APSE part.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2025-04-09 14:11 +0200 |
| Message-ID | <vt5o57$inuo$3@dont-email.me> |
| In reply to | #392250 |
On 09/04/2025 12:11, Michael S wrote: > On Wed, 9 Apr 2025 11:42:36 +0200 > David Brown <david.brown@hesbynett.no> wrote: > >> >> This applies to all languages. For example, in Python you do not >> have separate "interface" and "implementation" files - everything is >> in one ".py" file. If I have a Python module that says "import >> my_py_lib", how does Python know where to find "my_py_lib.py" ? How >> does it know which copy of "my_py_lib.py" to use from the dozen that >> I have on my computer? The answer is it uses some default rules for >> the language, some default rules for the implementation, some >> configuration settings, some flags, some run-time information >> (equivalent to compile-time information in compiled languages). The >> exact details are different, but the principle is the same for C and >> for any other language that can handle more than one file. >> > > It is not quite the same for all languages. The degree in which it is > standardizes vs left to implementation differs. In some languages it is > fully standardized. > I think, in case of Ada it was standardized in APSE. But then, real > world mostly accepted a language part of Ada standard and mostly > ignored APSE part. > > As I said, details vary, and some languages may specify more details than others. There are also differences in the relationship between a "module" of some sort that a unit might refer to, and the file or files that comprise that module. But the principle is that when one unit refers to another, the tools will have some way of figuring out which unit you are referring to, distinguishing it from other units or files on the same host system even if the filenames are the same. C does not differ in principle here from other languages. Bart seems to think C is somehow especially bad or complicated - he is wrong in that.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2025-04-09 13:16 +0300 |
| Message-ID | <20250409131633.000052f3@yahoo.com> |
| In reply to | #392246 |
On Wed, 9 Apr 2025 11:42:36 +0200 David Brown <david.brown@hesbynett.no> wrote: > On 08/04/2025 18:28, bart wrote: > > On 08/04/2025 15:50, David Brown wrote: > >> On 08/04/2025 13:35, bart wrote: > >> But it is true that some compilers have by default supported an > >> extension that was designed to make interoperability with Fortran > >> programs easier > > > > Which means a pile of badly written programs. > > That is why I said it was a bad idea for gcc to have "-fcommon" as > the default. It is a real shame that it took so long to change it. > > However, while that default meant that some people wrote C code with > a misunderstanding of linkages and the difference between > declarations and definitions, most C programmers don't make that > mistake. When gcc eventually changed the default, it did not lead to > wide-spread breakage of code. > I wouldn't be so sure. I have no statistics, but would expect that very significant part of Unix-only C programmers, especially grumpy old timers, believes that '-fcommon' is the real C and the rest are heresies.
[toc] | [prev] | [next] | [standalone]
Page 6 of 35 — ← Prev page 1 … 4 5 [6] 7 8 … 35 Next page →
Back to top | Article view | comp.lang.c
csiph-web