Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #169806 > unrolled thread
| Started by | Lynn McGuire <lynnmcguire5@gmail.com> |
|---|---|
| First post | 2023-04-03 18:20 -0500 |
| Last post | 2023-08-29 04:45 -0700 |
| Articles | 20 on this page of 182 — 29 participants |
Back to article view | Back to comp.lang.c
"Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Lynn McGuire <lynnmcguire5@gmail.com> - 2023-04-03 18:20 -0500
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Jim Kelly <invalid@invalid.net> - 2023-04-04 04:00 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Lynn McGuire <lynnmcguire5@gmail.com> - 2023-04-04 14:49 -0500
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Rene Kita <mail@rkta.de> - 2023-04-04 09:56 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan gazelle@shell.xmission.com (Kenny McCormack) - 2023-04-04 12:20 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan scott@slp53.sl.home (Scott Lurndal) - 2023-04-04 13:50 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Rene Kita <mail@rkta.de> - 2023-04-05 08:49 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan gazelle@shell.xmission.com (Kenny McCormack) - 2023-04-05 09:23 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-05 13:07 +0000
(realloc) Angels and pins (Was: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan) gazelle@shell.xmission.com (Kenny McCormack) - 2023-04-05 14:12 +0000
Re: (realloc) Angels and pins (Was: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan) cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-05 17:09 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-05 20:16 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-05 21:03 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-11 04:05 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan David Brown <david.brown@hesbynett.no> - 2023-04-05 17:05 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-04 11:30 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Lynn McGuire <lynnmcguire5@gmail.com> - 2023-04-04 14:51 -0500
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-05 01:10 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-05 00:42 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Opus <ifonly@youknew.org> - 2023-04-05 02:55 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-05 03:01 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-05 13:29 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan David Brown <david.brown@hesbynett.no> - 2023-04-05 17:15 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan scott@slp53.sl.home (Scott Lurndal) - 2023-04-05 15:27 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-05 10:40 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-05 18:55 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan David Brown <david.brown@hesbynett.no> - 2023-04-06 00:37 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-05 17:40 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-12 05:46 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-06 12:34 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan John Forkosh <forkosh@panix.com> - 2023-04-06 05:42 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan David Brown <david.brown@hesbynett.no> - 2023-04-07 12:16 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Kaz Kylheku <864-117-4973@kylheku.com> - 2023-04-07 11:38 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-09 07:23 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-09 17:04 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-09 19:34 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 09:45 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 14:52 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 17:29 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 11:48 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 18:10 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 12:19 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-04-10 09:55 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 10:41 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 11:22 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Bart <bc@freeuk.com> - 2023-04-10 21:22 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 14:22 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-10 22:36 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Bart <bc@freeuk.com> - 2023-04-11 00:11 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 11:34 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 15:37 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 11:57 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 17:26 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 14:27 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 18:45 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-11 04:50 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Spiros Bousbouras <spibou@gmail.com> - 2023-04-10 15:58 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 12:08 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 17:27 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-11 04:47 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 10:26 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 14:51 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 11:20 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 15:35 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 12:04 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 17:34 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-11 11:24 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-04-11 16:17 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Bart <bc@freeuk.com> - 2023-04-11 18:13 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-04-11 17:58 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-09 12:41 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 09:31 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 09:46 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 16:29 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 16:37 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 11:26 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 17:43 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 12:19 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 18:35 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Öö Tiib <ootiib@hot.ee> - 2023-04-10 10:02 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 20:14 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 11:34 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ike Naar <ike@sdf.org> - 2023-04-10 21:47 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-10 23:04 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Öö Tiib <ootiib@hot.ee> - 2023-04-11 01:08 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-11 11:26 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Öö Tiib <ootiib@hot.ee> - 2023-04-11 02:43 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-11 15:14 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-11 11:35 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-11 12:09 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-11 19:46 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-04-11 22:44 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan David Brown <david.brown@hesbynett.no> - 2023-04-12 09:46 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-12 02:35 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-04-13 22:26 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-09 06:12 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 13:10 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 19:11 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan scott@slp53.sl.home (Scott Lurndal) - 2023-04-10 17:22 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 19:33 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 19:41 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan scott@slp53.sl.home (Scott Lurndal) - 2023-04-10 18:13 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 11:30 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 10:53 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-11 11:25 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-11 11:25 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 11:13 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 20:27 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 11:54 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 21:01 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 19:06 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 21:20 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-10 19:46 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 13:17 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 13:16 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 14:54 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 20:44 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-11 05:01 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan David Brown <david.brown@hesbynett.no> - 2023-04-11 11:27 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-11 11:41 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-11 12:50 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan David Brown <david.brown@hesbynett.no> - 2023-04-12 09:51 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-12 09:12 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 09:58 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 09:54 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-04-10 11:21 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan jak <nospam@please.ty> - 2023-04-10 17:58 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-11 05:31 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-10 09:50 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-09 12:44 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-09 20:19 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-09 12:55 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-09 21:44 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-09 19:53 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-05 20:33 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-16 07:18 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-05 12:53 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-06 12:30 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-08 18:46 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-09 19:35 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-20 09:07 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-07-20 22:35 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan vallor <vallor@cultnix.org> - 2023-07-22 12:54 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-22 22:04 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan vallor <vallor@cultnix.org> - 2023-07-24 10:44 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-22 16:28 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan vallor <vallor@cultnix.org> - 2023-07-24 08:38 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-07-24 18:55 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan om@iki.fi (Otto J. Makela) - 2023-07-26 11:30 +0300
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-26 19:28 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-07 13:08 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-08-15 12:01 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-28 15:49 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-08-28 23:42 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Spiros Bousbouras <spibou@gmail.com> - 2023-08-29 00:51 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-08-29 01:20 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-05 18:24 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Phil Carmody <pc+usenet@asdf.org> - 2023-04-17 09:25 +0300
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-18 11:56 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-05-02 07:12 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Phil Carmody <pc+usenet@asdf.org> - 2023-05-07 09:37 +0300
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-20 09:09 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Lowell Gilbert <lgusenet@be-well.ilk.org> - 2023-04-04 21:19 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-05 03:36 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Opus <ifonly@youknew.org> - 2023-04-05 05:10 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Richard Damon <Richard@Damon-Family.org> - 2023-04-05 07:54 -0400
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Opus <ifonly@youknew.org> - 2023-04-05 21:31 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-16 06:12 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-05 09:20 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-05 10:07 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-05 20:23 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-05 21:20 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-06 17:03 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan cross@spitfire.i.gajendra.net (Dan Cross) - 2023-04-06 20:34 +0000
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-07 00:25 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-19 08:56 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-06 19:40 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-04-08 02:37 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-08 21:04 +0100
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-05-02 06:22 -0700
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Bonita Montero <Bonita.Montero@gmail.com> - 2023-08-09 16:00 +0200
Re: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan Michael S <already5chosen@yahoo.com> - 2023-08-29 04:45 -0700
Page 1 of 10 [1] 2 3 … 10 Next page →
| From | Lynn McGuire <lynnmcguire5@gmail.com> |
|---|---|
| Date | 2023-04-03 18:20 -0500 |
| Subject | "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan |
| Message-ID | <u0fn0g$34scf$1@dont-email.me> |
"Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly
with Special Guest Borer Yekai Pan
https://queue.acm.org/detail.cfm?id=3588242
"The Good News
A new major revision of the C language standard, C23, is due out this
year. We'll tour the highs and lows of the latest draft9 and then drill
down on the mother of all breaking changes. Sidebars celebrate C idioms
and undefined behavior with code and song, respectively."
"Unfilled Potholes and Festering Sores
Laws should be freely available, intelligible, and agreeable to the
governed, and they should keep pace with changing times. C23 lacks these
virtues."
Wow.
Lynn
[toc] | [next] | [standalone]
| From | Jim Kelly <invalid@invalid.net> |
|---|---|
| Date | 2023-04-04 04:00 +0100 |
| Message-ID | <u0g2kv$3iqib$1@paganini.bofh.team> |
| In reply to | #169806 |
On 04/04/2023 00:20, Lynn McGuire wrote: > "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly > with Special Guest Borer Yekai Pan > https://queue.acm.org/detail.cfm?id=3588242 > The same document in pdf format: <https://dl.acm.org/doi/pdf/10.1145/3588242>
[toc] | [prev] | [next] | [standalone]
| From | Lynn McGuire <lynnmcguire5@gmail.com> |
|---|---|
| Date | 2023-04-04 14:49 -0500 |
| Message-ID | <u0huve$3hrar$1@dont-email.me> |
| In reply to | #169807 |
On 4/3/2023 10:00 PM, Jim Kelly wrote: > On 04/04/2023 00:20, Lynn McGuire wrote: >> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >> with Special Guest Borer Yekai Pan >> https://queue.acm.org/detail.cfm?id=3588242 >> > > The same document in pdf format: > > <https://dl.acm.org/doi/pdf/10.1145/3588242> Thanks, I should have added that also. Lynn
[toc] | [prev] | [next] | [standalone]
| From | Rene Kita <mail@rkta.de> |
|---|---|
| Date | 2023-04-04 09:56 +0000 |
| Message-ID | <u0gs80$3cmm0$1@dont-email.me> |
| In reply to | #169806 |
Lynn McGuire <lynnmcguire5@gmail.com> wrote: > "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly > with Special Guest Borer Yekai Pan > https://queue.acm.org/detail.cfm?id=3588242 That was an interesting read. I stick to C99 I'll guess.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2023-04-04 12:20 +0000 |
| Message-ID | <u0h4n4$1usij$1@news.xmission.com> |
| In reply to | #169808 |
In article <u0gs80$3cmm0$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >Lynn McGuire <lynnmcguire5@gmail.com> wrote: >> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >> with Special Guest Borer Yekai Pan >> https://queue.acm.org/detail.cfm?id=3588242 > >That was an interesting read. I stick to C99 I'll guess. Just out of curiosity, what *is* the big breaking change? -- The randomly chosen signature file that would have appeared here is more than 4 lines long. As such, it violates one or more Usenet RFCs. In order to remain in compliance with said RFCs, the actual sig can be found at the following URL: http://user.xmission.com/~gazelle/Sigs/Snicker
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2023-04-04 13:50 +0000 |
| Message-ID | <jWVWL.261625$Sgyc.172759@fx40.iad> |
| In reply to | #169810 |
gazelle@shell.xmission.com (Kenny McCormack) writes: >In article <u0gs80$3cmm0$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >>Lynn McGuire <lynnmcguire5@gmail.com> wrote: >>> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >>> with Special Guest Borer Yekai Pan >>> https://queue.acm.org/detail.cfm?id=3588242 >> >>That was an interesting read. I stick to C99 I'll guess. > >Just out of curiosity, what *is* the big breaking change? A fatal change in the semantics of 'realloc'.
[toc] | [prev] | [next] | [standalone]
| From | Rene Kita <mail@rkta.de> |
|---|---|
| Date | 2023-04-05 08:49 +0000 |
| Message-ID | <u0jcmt$3r2ce$1@dont-email.me> |
| In reply to | #169810 |
Kenny McCormack <gazelle@shell.xmission.com> wrote: > In article <u0gs80$3cmm0$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >>Lynn McGuire <lynnmcguire5@gmail.com> wrote: >>> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >>> with Special Guest Borer Yekai Pan >>> https://queue.acm.org/detail.cfm?id=3588242 >> >>That was an interesting read. I stick to C99 I'll guess. > > Just out of curiosity, what *is* the big breaking change? realloc with a size of zero is UB in C23. There was some extended discussion on HN[0]. [0]: https://news.ycombinator.com/item?id=35404025
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2023-04-05 09:23 +0000 |
| Message-ID | <u0jem9$2033d$1@news.xmission.com> |
| In reply to | #169823 |
In article <u0jcmt$3r2ce$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >Kenny McCormack <gazelle@shell.xmission.com> wrote: >> In article <u0gs80$3cmm0$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >>>Lynn McGuire <lynnmcguire5@gmail.com> wrote: >>>> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >>>> with Special Guest Borer Yekai Pan >>>> https://queue.acm.org/detail.cfm?id=3588242 >>> >>>That was an interesting read. I stick to C99 I'll guess. >> >> Just out of curiosity, what *is* the big breaking change? > >realloc with a size of zero is UB in C23. Interesting. I had no idea that realloc with a size of zero is (was?) equivalent to a call to free() - until I read the man page a day or so ago and found that. So, no more...? -- The randomly chosen signature file that would have appeared here is more than 4 lines long. As such, it violates one or more Usenet RFCs. In order to remain in compliance with said RFCs, the actual sig can be found at the following URL: http://user.xmission.com/~gazelle/Sigs/RightWingMedia
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2023-04-05 13:07 +0000 |
| Message-ID | <u0jrr7$jvd$2@reader2.panix.com> |
| In reply to | #169824 |
In article <u0jem9$2033d$1@news.xmission.com>, Kenny McCormack <gazelle@shell.xmission.com> wrote: >In article <u0jcmt$3r2ce$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >>Kenny McCormack <gazelle@shell.xmission.com> wrote: >>> In article <u0gs80$3cmm0$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >>>>Lynn McGuire <lynnmcguire5@gmail.com> wrote: >>>>> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >>>>> with Special Guest Borer Yekai Pan >>>>> https://queue.acm.org/detail.cfm?id=3588242 >>>> >>>>That was an interesting read. I stick to C99 I'll guess. >>> >>> Just out of curiosity, what *is* the big breaking change? >> >>realloc with a size of zero is UB in C23. > >Interesting. > >I had no idea that realloc with a size of zero is (was?) equivalent to a >call to free() - until I read the man page a day or so ago and found that. > >So, no more...? The thing is, that is, and always has been, implementation defined. The authors presented it as a universal property of all implementations, but it just is not. To be explicit about it: realloc(ptr, 0); is not, and never has been, guaranteed to be equivalent to free(ptr). - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2023-04-05 14:12 +0000 |
| Subject | (realloc) Angels and pins (Was: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan) |
| Message-ID | <u0jvkb$20c26$1@news.xmission.com> |
| In reply to | #169826 |
In article <u0jrr7$jvd$2@reader2.panix.com>,
Dan Cross <cross@spitfire.i.gajendra.net> wrote:
...
>To be explicit about it: realloc(ptr, 0); is not, and never has
>been, guaranteed to be equivalent to free(ptr).
It is, on platforms where it is. A tautology, that.
Beyond that, I have no further interest in this, as we'd just be arguing
about angels and pins.
--
People sleep peaceably in their beds at night only because rough
men stand ready to do violence on their behalf.
George Orwell
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2023-04-05 17:09 +0000 |
| Subject | Re: (realloc) Angels and pins (Was: "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly with Special Guest Borer Yekai Pan) |
| Message-ID | <u0ka12$1l0$1@reader2.panix.com> |
| In reply to | #169829 |
In article <u0jvkb$20c26$1@news.xmission.com>, Kenny McCormack <gazelle@shell.xmission.com> wrote: >In article <u0jrr7$jvd$2@reader2.panix.com>, >Dan Cross <cross@spitfire.i.gajendra.net> wrote: >... >>To be explicit about it: realloc(ptr, 0); is not, and never has >>been, guaranteed to be equivalent to free(ptr). > >It is, on platforms where it is. A tautology, that. Or in C89 (I was wrong on that). >Beyond that, I have no further interest in this, as we'd just be arguing >about angels and pins. How portable are these pins? (I kid! I kid!) - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2023-04-05 20:16 +0100 |
| Message-ID | <87bkk26sx1.fsf@bsb.me.uk> |
| In reply to | #169826 |
cross@spitfire.i.gajendra.net (Dan Cross) writes: > In article <u0jem9$2033d$1@news.xmission.com>, > Kenny McCormack <gazelle@shell.xmission.com> wrote: >>In article <u0jcmt$3r2ce$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >>>Kenny McCormack <gazelle@shell.xmission.com> wrote: >>>> In article <u0gs80$3cmm0$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >>>>>Lynn McGuire <lynnmcguire5@gmail.com> wrote: >>>>>> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >>>>>> with Special Guest Borer Yekai Pan >>>>>> https://queue.acm.org/detail.cfm?id=3588242 >>>>> >>>>>That was an interesting read. I stick to C99 I'll guess. >>>> >>>> Just out of curiosity, what *is* the big breaking change? >>> >>>realloc with a size of zero is UB in C23. >> >>Interesting. >> >>I had no idea that realloc with a size of zero is (was?) equivalent to a >>call to free() - until I read the man page a day or so ago and found that. >> >>So, no more...? > > The thing is, that is, and always has been, implementation > defined. No, I don't think so. The /return value/ is, and always has been, implementation defined, but, in ANSI C (1989), realloc(ptr, 0) was defined to free the pointer. That changed in C99 (I think), though it was simply left unstated what would happen, so an implementation is not even obliged to document if it frees the pointer or not. > The authors presented it as a universal property of > all implementations, but it just is not. I don't think they do. They state that "The C89 and C99 standards committees strongly recommended that allocation interfaces malloc, calloc, and realloc return a null pointer in response to zero-byte requests" and that this "implies that realloc(p,0) should unconditionally free(p)". I don't know where that recommendation comes from (the PDF is missing footnotes > 27) and the implication seems to be a bit of a stretch, but if they just assumed this to be universal, why explain that it was recommended? > To be explicit about it: realloc(ptr, 0); is not, and never has > been, guaranteed to be equivalent to free(ptr). Have you checked ANSI C? I think it was guaranteed in those days, though I don't have an official copy. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2023-04-05 21:03 +0000 |
| Message-ID | <u0knnd$omi$1@reader2.panix.com> |
| In reply to | #169839 |
In article <87bkk26sx1.fsf@bsb.me.uk>, Ben Bacarisse <ben.usenet@bsb.me.uk> wrote: >cross@spitfire.i.gajendra.net (Dan Cross) writes: >[snip] >> To be explicit about it: realloc(ptr, 0); is not, and never has >> been, guaranteed to be equivalent to free(ptr). > >Have you checked ANSI C? I think it was guaranteed in those days, >though I don't have an official copy. I did, and indeed I was mistaken vis C89. See my other responses in this thread where I quote the standard. C99 and later explicitly say that the old value is deallocated and the new value allocated. However, one cannot detect the difference between an error condition and an implementation that returns NULL in response to a zero-sized allocation from the return value alone. I stand by my critique of the authors' code. - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2023-04-11 04:05 -0700 |
| Message-ID | <86a5ze4r2o.fsf@linuxsc.com> |
| In reply to | #169839 |
Ben Bacarisse <ben.usenet@bsb.me.uk> writes: > cross@spitfire.i.gajendra.net (Dan Cross) writes: [..concerning whether realloc() with a size of 0 must free()..] >> The authors presented it as a universal property of >> all implementations, but it just is not. > > I don't think they do. Right. > They state that "The C89 and C99 standards committees strongly > recommended that allocation interfaces malloc, calloc, and realloc > return a null pointer in response to zero-byte requests" and that > this "implies that realloc(p,0) should unconditionally free(p)". > I don't know where that recommendation comes from (the PDF is > missing footnotes > 27) I believe the authors mean to refer to statements in the two C Rationale documents (and indeed it is the case that these documents discuss matters concerning how memory management behave). > and the implication seems to be a bit of a stretch, but if they > just assumed this to be universal, why explain that it was > recommended? To me it seems clear that the authors mean to distinguish between what behaviors are /recommended/ (or at least that they think are recommended) and what behaviors are /described or specified/ by the various C standards over the years (which definitely have changed in different official releases of the C standard). And it seems obvious that the authors recognize that these two things are not the same.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-04-05 17:05 +0200 |
| Message-ID | <u0k2mt$3ubl4$1@dont-email.me> |
| In reply to | #169824 |
On 05/04/2023 11:23, Kenny McCormack wrote: > In article <u0jcmt$3r2ce$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >> Kenny McCormack <gazelle@shell.xmission.com> wrote: >>> In article <u0gs80$3cmm0$1@dont-email.me>, Rene Kita <mail@rkta.de> wrote: >>>> Lynn McGuire <lynnmcguire5@gmail.com> wrote: >>>>> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >>>>> with Special Guest Borer Yekai Pan >>>>> https://queue.acm.org/detail.cfm?id=3588242 >>>> >>>> That was an interesting read. I stick to C99 I'll guess. >>> >>> Just out of curiosity, what *is* the big breaking change? >> >> realloc with a size of zero is UB in C23. > > Interesting. > > I had no idea that realloc with a size of zero is (was?) equivalent to a > call to free() - until I read the man page a day or so ago and found that. It isn't equivalent to free(). It is implementation-dependent. And while /some/ implementations handle it like free(), others do not. Bizarrely, the article authors seem to believe this is guaranteed behaviour while also giving references to pages showing a range of different behaviour in real-world C libraries. (And we are not talking about old, nice or obscure libraries.) The article is complete nonsense. It is published 3 days early - it really is a joke. There is very little justification for their viewpoints in the standards, and very little match between what they say is in the standards, and what is really there. Basically, a particular unusual use-case of realloc has changed from implementation-dependent behaviour (where the implementations vary so much you can't use it in portable code) to undefined behaviour (which in real life means different libraries will continue to keep their current differing behaviours). And the authors write as though this is the end of the C world as we know it. /You/ had no idea what happens when realloc'ing with a size of zero. That's fine - it's not something that makes much sense, and I doubt if many programmers know what it does. An even smaller proportion will be correct in what they think they know. If you are writing sensible and reasonably portable code, there is no change. (The article also talks a bit about how difficult the standards sometimes are to understand - that's true enough, but nothing new in C23.) > > So, no more...? >
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2023-04-04 11:30 +0000 |
| Message-ID | <u0h1p8$ip0$1@reader2.panix.com> |
| In reply to | #169806 |
In article <u0fn0g$34scf$1@dont-email.me>, Lynn McGuire <lynnmcguire5@gmail.com> wrote: >"Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >with Special Guest Borer Yekai Pan > https://queue.acm.org/detail.cfm?id=3588242 >[snip] Yikes. That article is truly awful. ACM should be ashamed. - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Lynn McGuire <lynnmcguire5@gmail.com> |
|---|---|
| Date | 2023-04-04 14:51 -0500 |
| Message-ID | <u0hv4n$3hrar$2@dont-email.me> |
| In reply to | #169809 |
On 4/4/2023 6:30 AM, Dan Cross wrote: > In article <u0fn0g$34scf$1@dont-email.me>, > Lynn McGuire <lynnmcguire5@gmail.com> wrote: >> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >> with Special Guest Borer Yekai Pan >> https://queue.acm.org/detail.cfm?id=3588242 >> [snip] > > Yikes. That article is truly awful. > > ACM should be ashamed. > > - Dan C. Written by real programmers, not journalists. What do you expect ? Not everyone is Donald Knuth or Niklaus Wirth. Lynn
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2023-04-05 01:10 +0100 |
| Message-ID | <87zg7n89zw.fsf@bsb.me.uk> |
| In reply to | #169813 |
Lynn McGuire <lynnmcguire5@gmail.com> writes: > On 4/4/2023 6:30 AM, Dan Cross wrote: >> In article <u0fn0g$34scf$1@dont-email.me>, >> Lynn McGuire <lynnmcguire5@gmail.com> wrote: >>> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >>> with Special Guest Borer Yekai Pan >>> https://queue.acm.org/detail.cfm?id=3588242 >>> [snip] >> Yikes. That article is truly awful. >> ACM should be ashamed. >> - Dan C. > > Written by real programmers, not journalists. What do you expect ? Not > everyone is Donald Knuth or Niklaus Wirth. I would expect a more serious tone from an ACM publication, but the journal (ACMQUEUE) is one I don't know and it may well have a more relaxed editorial policy than I am used to. I don't like hyperbole and sarcasm in technical publications but I am not "down with the kids" these days. But their example stack code lends itself to a puzzle: on what implementation assumptions does it depend? I believe it is not fully portable for reasons that are unrelated to the realloc implementation. This is not, technically speaking, a bug since I have no reason to suppose the code was intended to be portable across all conforming C implementations, but I'd have pointed it out, had I been a reviewer, since it's an unnecessary distraction to the reader. I agree with the authors that the change declaring realloc(..., 0) to be undefined is worrying, but I can't follow their reasoning about the history. They suggest something had already happened in C17 that set C on a course towards this "breaking change" but I can't find what they refer to. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2023-04-05 00:42 +0000 |
| Message-ID | <u0ig61$64g$1@reader2.panix.com> |
| In reply to | #169814 |
In article <87zg7n89zw.fsf@bsb.me.uk>, Ben Bacarisse <ben.usenet@bsb.me.uk> wrote: >Lynn McGuire <lynnmcguire5@gmail.com> writes: > >> On 4/4/2023 6:30 AM, Dan Cross wrote: >>> In article <u0fn0g$34scf$1@dont-email.me>, >>> Lynn McGuire <lynnmcguire5@gmail.com> wrote: >>>> "Catch-23: The New C Standard,Sets the World on Fire" by Terence Kelly >>>> with Special Guest Borer Yekai Pan >>>> https://queue.acm.org/detail.cfm?id=3588242 >>>> [snip] >>> Yikes. That article is truly awful. >>> ACM should be ashamed. >>> - Dan C. >> >> Written by real programmers, not journalists. What do you expect ? Not >> everyone is Donald Knuth or Niklaus Wirth. > >I would expect a more serious tone from an ACM publication, but the >journal (ACMQUEUE) is one I don't know and it may well have a more >relaxed editorial policy than I am used to. I don't like hyperbole and >sarcasm in technical publications but I am not "down with the kids" >these days. > >But their example stack code lends itself to a puzzle: on what >implementation assumptions does it depend? I believe it is not fully >portable for reasons that are unrelated to the realloc implementation. >This is not, technically speaking, a bug since I have no reason to >suppose the code was intended to be portable across all conforming C >implementations, but I'd have pointed it out, had I been a reviewer, >since it's an unnecessary distraction to the reader. > >I agree with the authors that the change declaring realloc(..., 0) to be >undefined is worrying, but I can't follow their reasoning about the >history. They suggest something had already happened in C17 that set C >on a course towards this "breaking change" but I can't find what they >refer to. The authors, bluntly, wrong: the behavior of realloc() when the size argument is 0, the implementation is, as it always has been since C89, implementation defined. Moreoever, there's no way to tell whether the underlying object was actually free'd or not from the return alone, and checking `errno` is not portable. The proposal to make realloc with size 0 UB is not bad here: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2464.pdf The authors tried to make it out like their code was portable and well-defined. It was not. That combined with the little quips about "neurodivergent" ideas or about marijuana legalization (really?) smack of proud ignorance. That they can't understand at all what `unreachable` may be used for makes me think that they may not have as good of a handle on the language as they claim. Oh, and among the people championing having `malloc(0)` return a non-NULL pointer were Rob Pike and Doug McIlroy. Not that one need appeal to authority, but the article's authors would have done well to at least, perhaps, listen to some of the viewpoints of folks from the lab where C was born before pouring derision on ideas that they didn't seem to have a great understanding of. - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Opus <ifonly@youknew.org> |
|---|---|
| Date | 2023-04-05 02:55 +0200 |
| Message-ID | <u0igup$3kgn0$1@dont-email.me> |
| In reply to | #169815 |
Le 05/04/2023 à 02:42, Dan Cross a écrit : > The authors, bluntly, wrong: the behavior of realloc() when the > size argument is 0, the implementation is, as it always has > been since C89, implementation defined. Yes, it's actually the case for all memory allocation functions (malloc, calloc, realloc): " If the size of the space requested is zero, the behavior is implementation-defined: either a null pointer is returned, or the behavior is as if the size were some nonzero value, except that the returned pointer shall not be used to access an object." > The authors tried to make it out like their code was portable > and well-defined. It was not. Indeed. If you use implementationd-defined behaviors, you should know what to expect and document it appropriately. Do not expect it to still be doing what you expected with any other implementation. I've personally never used this implementation-defined behavior and try to avoid all of them in general as much as is practical. > That combined with the little quips about "neurodivergent" ideas > or about marijuana legalization (really?) smack of proud > ignorance. That they can't understand at all what `unreachable` > may be used for makes me think that they may not have as good of > a handle on the language as they claim. It read a bit like a tantrum with a clickbaity title. > Oh, and among the people championing having `malloc(0)` return a > non-NULL pointer were Rob Pike and Doug McIlroy. Not that one > need appeal to authority, but the article's authors would have > done well to at least, perhaps, listen to some of the viewpoints > of folks from the lab where C was born before pouring derision > on ideas that they didn't seem to have a great understanding of. malloc(0) has the same behavior as realloc(xx, 0) as I quoted above. The behavior is implementation-defined, and even when it does not return a null pointer, you're not supposed to dereference it.
[toc] | [prev] | [next] | [standalone]
Page 1 of 10 [1] 2 3 … 10 Next page →
Back to top | Article view | comp.lang.c
csiph-web