Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #110663 > unrolled thread
| Started by | bartc <bc@freeuk.com> |
|---|---|
| First post | 2017-05-26 01:01 +0100 |
| Last post | 2017-05-28 22:15 -0700 |
| Articles | 5 on this page of 205 — 28 participants |
Back to article view | Back to comp.lang.c
C Code Quality bartc <bc@freeuk.com> - 2017-05-26 01:01 +0100
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-26 03:18 +0100
Re: C Code Quality "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-05-25 20:03 -0700
Re: C Code Quality Gareth Owen <gwowen@gmail.com> - 2017-05-26 06:32 +0100
Re: C Code Quality Richard Heathfield <rjh@cpax.org.uk> - 2017-05-26 07:24 +0100
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 11:33 +0100
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 15:16 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 14:40 +0100
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 16:42 +0200
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-26 17:42 +0200
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-26 17:46 +0200
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-26 19:09 +0200
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-26 19:48 +0200
Re: C Code Quality "James R. Kuyper" <jameskuyper@verizon.net> - 2017-05-26 12:05 -0400
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-26 19:10 +0200
Re: C Code Quality "James R. Kuyper" <jameskuyper@verizon.net> - 2017-05-26 13:16 -0400
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-27 02:18 +0200
Re: C Code Quality raltbos@xs4all.nl (Richard Bos) - 2017-05-29 10:07 +0000
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-29 12:21 +0200
Re: C Code Quality raltbos@xs4all.nl (Richard Bos) - 2017-05-29 12:00 +0000
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-29 14:23 +0200
Re: C Code Quality Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-29 10:57 -0400
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-29 17:16 +0200
Re: C Code Quality Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-29 16:53 -0400
Re: C Code Quality raltbos@xs4all.nl (Richard Bos) - 2017-05-29 15:23 +0000
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-29 17:25 +0200
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-29 14:13 +0100
Re: C Code Quality Gareth Owen <gwowen@gmail.com> - 2017-05-29 14:48 +0100
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-29 17:14 +0200
Re: C Code Quality Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-29 16:57 -0400
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-29 23:44 +0200
Re: C Code Quality Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-29 19:14 -0400
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-30 02:57 +0200
Re: C Code Quality Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-29 22:23 -0400
Re: C Code Quality Gareth Owen <gwowen@gmail.com> - 2017-05-30 06:54 +0100
Re: C Code Quality asetofsymbols@gmail.com - 2017-05-29 15:06 -0700
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-30 00:23 +0200
Re: C Code Quality asetofsymbols@gmail.com - 2017-05-29 15:33 -0700
Re: C Code Quality Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-29 19:15 -0400
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-30 02:55 +0200
Re: C Code Quality Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-29 22:24 -0400
Re: C Code Quality David Kleinecke <dkleinecke@gmail.com> - 2017-05-30 15:24 -0700
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-31 00:48 +0200
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-05-30 06:04 -0700
Re: C Code Quality scott@slp53.sl.home (Scott Lurndal) - 2017-05-30 14:21 +0000
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-30 17:31 +0200
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-30 17:48 +0200
Re: C Code Quality raltbos@xs4all.nl (Richard Bos) - 2017-06-03 12:07 +0000
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-06-05 13:10 -0700
Re: C Code Quality "Patrick.Schluter" <Patrick.Schluter@free.fr> - 2017-05-30 23:46 +0200
Re: C Code Quality raltbos@xs4all.nl (Richard Bos) - 2017-06-03 12:09 +0000
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 09:09 -0700
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-26 19:11 +0200
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 20:18 +0200
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-27 02:59 +0200
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-27 14:52 +0200
Re: C Code Quality supercat@casperkitty.com - 2017-05-27 13:51 -0700
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-27 22:36 +0100
Re: C Code Quality supercat@casperkitty.com - 2017-05-28 09:38 -0700
Re: C Code Quality "Patrick.Schluter" <Patrick.Schluter@free.fr> - 2017-05-26 20:31 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 19:47 +0100
Re: C Code Quality "Patrick.Schluter" <Patrick.Schluter@free.fr> - 2017-05-26 21:50 +0200
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 13:06 -0700
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 21:28 +0100
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 23:46 +0100
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-26 17:22 +0200
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-26 17:32 +0200
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-26 19:07 +0200
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-26 19:40 +0200
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 08:26 -0700
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 14:29 +0100
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 16:44 +0200
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 08:32 -0700
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 18:47 +0100
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 20:27 +0200
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 11:24 -0700
Re: C Code Quality Ike Naar <ike@iceland.freeshell.org> - 2017-05-28 07:25 +0000
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-26 17:44 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 17:31 +0100
Re: C Code Quality Keith Thompson <kst-u@mib.org> - 2017-05-26 09:52 -0700
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 20:29 +0200
Re: C Code Quality "James R. Kuyper" <jameskuyper@verizon.net> - 2017-05-26 14:41 -0400
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 08:22 -0700
Re: C Code Quality scott@slp53.sl.home (Scott Lurndal) - 2017-05-26 16:26 +0000
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 10:06 -0700
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 20:37 +0200
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 12:24 -0700
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-27 02:03 +0100
Re: C Code Quality Noob <root@127.0.0.1> - 2017-05-28 00:07 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-27 23:51 +0100
Re: C Code Quality Gareth Owen <gwowen@gmail.com> - 2017-05-28 10:52 +0100
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-28 16:03 +0200
Re: C Code Quality Philip Lantz <prl@canterey.us> - 2017-05-25 20:37 -0700
Re: C Code Quality Philip Lantz <prl@canterey.us> - 2017-05-25 20:42 -0700
C Code Quality asetofsymbols@gmail.com - 2017-05-25 23:58 -0700
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 12:53 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 12:32 +0100
Re: C Code Quality mark.bluemel@gmail.com - 2017-05-26 06:21 -0700
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 15:25 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 15:00 +0100
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 16:50 +0200
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-26 17:14 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 17:24 +0100
Re: C Code Quality scott@slp53.sl.home (Scott Lurndal) - 2017-05-26 16:46 +0000
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-26 20:47 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-27 19:31 +0100
Re: C Code Quality Noob <root@127.0.0.1> - 2017-05-27 10:52 +0200
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-28 18:57 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-28 20:00 +0100
Re: C Code Quality Ian Collins <ian-news@hotmail.com> - 2017-05-29 07:34 +1200
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-29 11:32 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-29 12:37 +0100
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-29 14:01 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-29 13:47 +0100
Re: C Code Quality Reinhardt Behm <rbehm@hushmail.com> - 2017-05-29 20:15 +0800
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-29 14:23 +0100
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-29 17:36 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-29 17:01 +0100
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-30 07:05 -0700
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-30 17:18 +0200
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-30 21:31 +0200
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-30 12:49 -0700
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-30 13:52 -0700
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-31 12:55 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-31 13:15 +0100
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-31 05:42 -0700
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-31 15:40 +0100
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-31 10:52 -0700
Re: C Code Quality bartc <bc@freeuk.com> - 2017-06-01 00:00 +0100
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 01:11 +0100
Re: C Code Quality bartc <bc@freeuk.com> - 2017-06-01 02:21 +0100
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-06-01 10:37 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-06-01 11:28 +0100
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 10:55 +0100
Re: C Code Quality bartc <bc@freeuk.com> - 2017-06-06 12:43 +0100
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-06 13:03 +0100
Re: C Code Quality bartc <bc@freeuk.com> - 2017-06-06 14:44 +0100
Re: C Code Quality scott@slp53.sl.home (Scott Lurndal) - 2017-06-06 14:58 +0000
Re: C Code Quality bartc <bc@freeuk.com> - 2017-06-06 17:23 +0100
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-06 17:23 +0100
Re: C Code Quality antispam@math.uni.wroc.pl - 2017-06-06 17:14 +0000
Re: C Code Quality antispam@math.uni.wroc.pl - 2017-06-06 16:54 +0000
Re: C Code Quality bartc <bc@freeuk.com> - 2017-06-06 18:49 +0100
Re: C Code Quality antispam@math.uni.wroc.pl - 2017-06-06 18:28 +0000
Re: C Code Quality antispam@math.uni.wroc.pl - 2017-06-16 15:28 +0000
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-31 05:21 -0700
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-31 15:22 +0200
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-31 06:59 -0700
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-05-31 17:18 +0200
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-31 10:24 -0700
Re: C Code Quality David Kleinecke <dkleinecke@gmail.com> - 2017-05-31 12:22 -0700
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-31 22:32 +0100
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-31 23:08 +0100
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-06-01 00:22 +0200
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 00:54 +0100
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-06-01 04:00 -0700
Re: C Code Quality Keith Thompson <kst-u@mib.org> - 2017-06-01 09:12 -0700
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-06-01 10:09 -0700
Re: C Code Quality Keith Thompson <kst-u@mib.org> - 2017-06-01 10:11 -0700
Re: C Code Quality David Kleinecke <dkleinecke@gmail.com> - 2017-05-31 21:31 -0700
Re: C Code Quality David Kleinecke <dkleinecke@gmail.com> - 2017-05-31 21:27 -0700
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 11:04 +0100
Re: C Code Quality David Kleinecke <dkleinecke@gmail.com> - 2017-06-01 10:57 -0700
Re: C Code Quality Keith Thompson <kst-u@mib.org> - 2017-06-01 12:05 -0700
Re: C Code Quality "James R. Kuyper" <jameskuyper@verizon.net> - 2017-06-01 15:39 -0400
Re: C Code Quality supercat@casperkitty.com - 2017-06-01 13:39 -0700
Re: C Code Quality Keith Thompson <kst-u@mib.org> - 2017-06-01 14:19 -0700
Re: C Code Quality supercat@casperkitty.com - 2017-06-01 16:33 -0700
Re: C Code Quality David Kleinecke <dkleinecke@gmail.com> - 2017-06-01 15:22 -0700
Re: C Code Quality Keith Thompson <kst-u@mib.org> - 2017-06-01 17:44 -0700
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-02 02:56 +0100
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 21:24 +0100
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-06-01 04:13 -0700
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 14:01 +0100
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-06-01 06:53 -0700
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 15:13 +0100
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-06-01 08:40 -0700
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 17:18 +0100
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-06-01 14:56 -0700
Re: C Code Quality Ian Collins <ian-news@hotmail.com> - 2017-06-01 07:35 +1200
Re: C Code Quality David Brown <david.brown@hesbynett.no> - 2017-06-01 10:41 +0200
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-31 17:14 +0200
Re: C Code Quality Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2017-05-31 09:02 -0700
Re: C Code Quality GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-05-31 19:45 +0200
Re: C Code Quality raltbos@xs4all.nl (Richard Bos) - 2017-06-03 12:17 +0000
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-30 16:32 +0100
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-30 12:38 -0700
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-05-30 13:00 -0700
Re: C Code Quality Thiago Adams <thiago.adams@gmail.com> - 2017-06-02 10:58 -0700
Re: C Code Quality guido <guido@invalid.invalid> - 2017-05-30 19:56 +0000
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-30 23:06 +0100
Re: C Code Quality guido <guido@invalid.invalid> - 2017-05-30 23:02 +0000
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-31 04:14 +0100
Re: C Code Quality guido <guido@invalid.invalid> - 2017-05-31 08:38 +0000
Re: C Code Quality Ian Collins <ian-news@hotmail.com> - 2017-05-30 15:22 +1200
Re: C Code Quality raltbos@xs4all.nl (Richard Bos) - 2017-05-29 10:12 +0000
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-26 18:03 +0200
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 17:45 +0100
Re: C Code Quality Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-26 20:05 +0100
Re: C Code Quality supercat@casperkitty.com - 2017-05-26 12:42 -0700
Re: C Code Quality bartc <bc@freeuk.com> - 2017-05-26 20:19 +0100
Re: C Code Quality "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-05-27 03:03 +0200
Re: C Code Quality Keith Thompson <kst-u@mib.org> - 2017-05-26 20:37 -0700
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-05-28 22:17 -0700
Re: C Code Quality Tim Rentsch <txr@alumni.caltech.edu> - 2017-05-28 22:15 -0700
Page 11 of 11 — ← Prev page 1 … 9 10 [11]
| From | bartc <bc@freeuk.com> |
|---|---|
| Date | 2017-05-26 20:19 +0100 |
| Message-ID | <Zc%VA.113647$S_.55590@fx20.am4> |
| In reply to | #110721 |
On 26/05/2017 17:03, Pascal J. Bourguignon wrote: > bartc <bc@freeuk.com> writes: >> Here's a challenge: try and do without macros for one whole week. Then >> I bet you'll be able to manage with a lot fewer afterwards. The result >> should be cleaner, more obvious code. > > This is just impossible. FILE is a macro. printf may be a macro (and > probably is if you use gcc). I meant without writing new ones. Otherwise the standard library, and much existing code, will be full of macros (but I don't think FILE is one). -- bartc
[toc] | [prev] | [next] | [standalone]
| From | "Pascal J. Bourguignon" <pjb@informatimago.com> |
|---|---|
| Date | 2017-05-27 03:03 +0200 |
| Message-ID | <m2vaonru0e.fsf@despina.home> |
| In reply to | #110755 |
bartc <bc@freeuk.com> writes: > On 26/05/2017 17:03, Pascal J. Bourguignon wrote: >> bartc <bc@freeuk.com> writes: > >>> Here's a challenge: try and do without macros for one whole week. Then >>> I bet you'll be able to manage with a lot fewer afterwards. The result >>> should be cleaner, more obvious code. >> >> This is just impossible. FILE is a macro. printf may be a macro (and >> probably is if you use gcc). > > I meant without writing new ones. > > Otherwise the standard library, and much existing code, will be full > of macros (but I don't think FILE is one). Then why do you think it's FILE and not File or file? -- __Pascal J. Bourguignon http://www.informatimago.com
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <kst-u@mib.org> |
|---|---|
| Date | 2017-05-26 20:37 -0700 |
| Message-ID | <ln8tljt1fx.fsf@kst-u.example.com> |
| In reply to | #110779 |
"Pascal J. Bourguignon" <pjb@informatimago.com> writes:
> bartc <bc@freeuk.com> writes:
[...]
>> Otherwise the standard library, and much existing code, will be full
>> of macros (but I don't think FILE is one).
>
> Then why do you think it's FILE and not File or file?
The standard says that FILE is a type. The most obvious implementation
is a typedef. I suppose it could be a macro for a type name, like
"struct something", but the fact that the standard lists the macros
defined in <stdio.h>, and FILE isn't one of them, suggests that that's
not the intent.
I had speculated that FILE might have predated the existence of typedef.
I just took a look at some old UNIX sources from
https://github.com/dspinellis/unix-history-repo
and it's not clear whether that's the case or not.
In Research-V6, there is no stdio.h, and the C compiler doesn't
implement typedef.
In Research-V7, there is a stdio.h file; it defines FILE as a macro:
#define FILE struct _iobuf
The C compiler does implement typedef.
It was changed from a macro to a typedef some time between BSD-4_3
(1986) and BSD_4_4 (1993) -- and it's a typedef (and not also a macro)
on the system I'm using now.
In any case, the convention of using all-caps for macro names is not
universally followed; see bool in <stdbool.h>, for example.
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <txr@alumni.caltech.edu> |
|---|---|
| Date | 2017-05-28 22:17 -0700 |
| Message-ID | <kfnzidwdyws.fsf@x-alumni2.alumni.caltech.edu> |
| In reply to | #110703 |
bartc <bc@freeuk.com> writes: > Here's a challenge: try and do without macros for one whole week. I will do that, if you will agree not to bitch, whine or complain about C or how C is used, for the same length of time.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <txr@alumni.caltech.edu> |
|---|---|
| Date | 2017-05-28 22:15 -0700 |
| Message-ID | <kfn4lw4fdm1.fsf@x-alumni2.alumni.caltech.edu> |
| In reply to | #110663 |
bartc <bc@freeuk.com> writes: > I'm of the opinion that C's preprocessor plus its 'anything goes' > approach to writing declarations and such, can lead to poor code > that is very hard to follow. > > Most here seem to disagree. Unequivocally false. Of course use of the C preprocessor can lead to poor code that is very hard to follow, and every C developer with any significant experience can attest to that. And just by the way, the same can be said of any other non-trivial language facility. See Flon's Law - "There has never been, nor will there ever be, a programming language in which it is the least bit hard to write bad programs." (Disclaimer: that's from memory of reading the original, now many, many years ago.)
[toc] | [prev] | [standalone]
Page 11 of 11 — ← Prev page 1 … 9 10 [11]
Back to top | Article view | comp.lang.c
csiph-web