Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #59888 > unrolled thread
| Started by | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| First post | 2015-04-10 20:54 +0000 |
| Last post | 2015-04-18 08:11 -0700 |
| Articles | 11 on this page of 211 — 35 participants |
Back to article view | Back to comp.lang.c
Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-10 20:54 +0000
Re: Problems with va_list & friends... Andrew Cooper <amc96@cam.ac.uk> - 2015-04-10 22:36 +0100
Re: Problems with va_list & friends... Martin Shobe <martin.shobe@yahoo.com> - 2015-04-10 16:47 -0500
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-10 16:50 -0500
Re: Problems with va_list & friends... Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-04-10 15:33 -0700
Re: Problems with va_list & friends... Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-04-10 23:02 +0100
Re: Problems with va_list & friends... Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-04-11 03:00 +0000
Re: Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-11 03:18 +0000
Re: Problems with va_list & friends... Richard Damon <Richard@Damon-Family.org> - 2015-04-11 00:04 -0400
Re: Problems with va_list & friends... Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-04-11 16:02 +0000
Re: Problems with va_list & friends... Ian Collins <ian-news@hotmail.com> - 2015-04-12 08:27 +1200
Re: Problems with va_list & friends... Richard Damon <Richard@Damon-Family.org> - 2015-04-11 17:48 -0400
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-12 01:06 -0500
Re: Problems with va_list & friends... Martin Shobe <martin.shobe@yahoo.com> - 2015-04-11 10:49 -0500
Re: Problems with va_list & friends... Lőrinczy Zsigmond <nospam@for.me> - 2015-04-12 17:58 +0200
Re: Problems with va_list & friends... Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-04-13 17:31 +0000
Re: Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-13 17:48 +0000
Re: Problems with va_list & friends... Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-04-14 20:26 +0000
Re: Problems with va_list & friends... Noob <root@127.0.0.1> - 2015-04-14 22:58 +0200
Re: Problems with va_list & friends... Philipp Klaus Krause <pkk@spth.de> - 2015-04-16 13:08 +0200
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-16 12:14 -0500
Re: Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-16 17:18 +0000
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-16 18:43 +0100
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-16 21:03 -0500
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-16 23:38 -0400
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-17 07:39 +0100
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-17 13:31 -0500
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-17 14:46 -0400
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 11:46 -0700
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-18 15:35 -0700
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-22 10:57 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-19 11:58 +0100
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 10:50 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 17:55 +0100
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-17 23:01 -0500
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-18 00:24 -0500
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-18 07:50 -0400
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 11:56 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-19 14:59 +0100
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-19 11:47 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-19 18:44 +0100
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-19 18:34 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 01:42 -0700
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 08:14 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 10:30 -0700
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 13:56 -0400
Re: Problems with va_list & friends... Ian Pilcher <arequipeno@gmail.com> - 2015-04-20 18:39 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-23 12:37 -0700
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-23 20:25 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-24 07:58 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-24 12:58 -0500
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-24 22:13 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-28 13:05 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-30 08:40 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-01 08:40 -0700
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-05-03 11:42 -0500
Re: Problems with va_list & friends... Ian Collins <ian-news@hotmail.com> - 2015-05-04 17:43 +1200
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-05-04 07:34 -0500
Re: Problems with va_list & friends... Phil Carmody <pc+usenet@asdf.org> - 2015-05-08 17:12 +0300
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-10 07:40 -0700
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-05-04 08:49 -0700
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-05-04 12:23 -0500
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-20 07:49 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 14:27 +0100
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 09:39 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 17:48 +0100
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 15:58 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 22:25 +0100
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 13:22 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 11:15 -0700
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 15:02 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 12:51 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 21:17 +0100
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-20 16:09 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-21 00:33 +0100
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 16:26 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 15:46 -0700
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-20 16:17 -0700
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-21 07:43 -0700
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-21 08:06 -0700
Re: Problems with va_list & friends... Philip Lantz <prl@canterey.us> - 2015-04-22 21:55 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 20:04 +0100
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 13:22 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 21:42 +0100
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 16:58 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-21 01:16 +0100
Re: Problems with va_list & friends... Melzzzzz <mel@zzzzz.com> - 2015-04-21 02:19 +0200
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 23:14 -0700
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-21 11:47 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-22 00:13 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 08:36 +0100
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-22 03:15 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 11:52 +0100
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-22 09:04 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 17:14 +0100
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-20 15:24 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-21 00:24 -0500
Re: Problems with va_list & friends... raltbos@xs4all.nl (Richard Bos) - 2015-04-21 09:33 +0000
Re: Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-21 11:57 +0000
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-21 10:22 -0500
The Metric system (Was: Problems with va_list & friends...) gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-21 15:38 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Greg Martin <greg.at.softsprocket@dot.com> - 2015-04-21 15:58 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-21 18:09 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Greg Martin <greg.at.softsprocket@dot.com> - 2015-04-21 17:42 +0000
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-22 10:47 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Ian Collins <ian-news@hotmail.com> - 2015-04-22 20:56 +1200
Re: The Metric system (Was: Problems with va_list & friends...) guinness.tony@gmail.com - 2015-04-22 03:53 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 11:01 -0500
Re: The Metric system (Was: Problems with va_list & friends...) gwowen <gwowen@gmail.com> - 2015-04-23 08:17 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 10:21 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 11:17 -0500
Re: The Metric system (Was: Problems with va_list & friends...) David Kleinecke <dkleinecke@gmail.com> - 2015-04-22 09:59 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-22 18:48 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 14:35 -0500
Re: The Metric system Ben Bacarisse <ben.lists@bsb.me.uk> - 2015-04-22 21:22 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 09:58 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-25 12:33 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 12:18 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-25 13:51 +0100
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-25 16:34 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-25 17:00 +0100
Re: The Metric system (Was: Problems with va_list & friends...) gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-25 16:59 +0000
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-28 16:04 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-30 04:22 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Martin Shobe <martin.shobe@yahoo.com> - 2015-04-30 09:27 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Robert Wessel <robertwessel2@yahoo.com> - 2015-04-30 12:01 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-30 13:38 +0100
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-25 16:36 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Ian Collins <ian-news@hotmail.com> - 2015-04-26 08:20 +1200
Re: The Metric system (Was: Problems with va_list & friends...) "Bill Davy" <Bill@SynectixLtd.com> - 2015-04-25 21:33 +0100
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-26 12:07 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-26 14:22 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-26 15:44 +0000
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-22 13:11 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Robert Wessel <robertwessel2@yahoo.com> - 2015-04-22 17:05 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-22 18:30 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 17:35 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-22 19:15 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-23 11:05 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-23 12:54 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-23 14:12 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-23 15:50 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-23 16:43 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-23 18:09 -0400
Re: The Metric system (Was: Problems with va_list & friends...) "Osmium" <r124c4u102@comcast.net> - 2015-04-22 13:15 -0500
Re: The Metric system (Was: Problems with va_list & friends...) gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-22 19:17 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 20:48 +0100
Re: The Metric system (Was: Problems with va_list & friends...) "Osmium" <r124c4u102@comcast.net> - 2015-04-23 08:11 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-23 12:58 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Robert Wessel <robertwessel2@yahoo.com> - 2015-04-23 14:13 -0500
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 10:08 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 17:15 -0500
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 09:18 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-25 13:02 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-26 14:26 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Philip Lantz <prl@canterey.us> - 2015-05-03 11:48 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-05-05 18:20 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-05-05 12:43 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-22 11:32 +0100
Re: The Metric system (Was: Problems with va_list & friends...) "Bill Davy" <Bill@SynectixLtd.com> - 2015-04-22 14:31 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Ian Collins <ian-news@hotmail.com> - 2015-04-23 07:51 +1200
Re: The Metric system (Was: Problems with va_list & friends...) "Bill Davy" <Bill@SynectixLtd.com> - 2015-04-23 08:05 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 10:10 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-26 09:27 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-26 10:55 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Morris Dovey <mrdovey@iedu.com> - 2015-04-26 07:19 -0500
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-26 12:59 +0000
Re: The Metric system (Was: Problems with va_list & friends...) gwowen <gwowen@gmail.com> - 2015-04-28 07:07 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Morris Dovey <mrdovey@iedu.com> - 2015-04-28 09:51 -0500
Re: The Metric system (Was: Problems with va_list & friends...) guinness.tony@gmail.com - 2015-04-28 08:04 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-28 16:19 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Les Cargill <lcargill99@comcast.com> - 2015-04-28 19:15 -0500
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-28 16:06 +0000
Re: The Metric system (Was: Problems with va_list & friends...) guinness.tony@gmail.com - 2015-04-28 09:39 -0700
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-28 16:51 +0000
Re: The Metric system (Was: Problems with va_list & friends...) guinness.tony@gmail.com - 2015-04-29 05:08 -0700
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-29 13:47 +0000
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-28 13:03 -0400
Re: The Metric system (Was: Problems with va_list & friends...) David Thompson <dave.thompson2@verizon.net> - 2015-05-10 12:24 -0400
Re: The Metric system (Was: Problems with va_list & friends...) gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-21 18:12 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Greg Martin <greg.at.softsprocket@dot.com> - 2015-04-21 19:34 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-21 12:46 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Ian Collins <ian-news@hotmail.com> - 2015-04-22 07:42 +1200
Re: The Metric system (Was: Problems with va_list & friends...) Greg Martin <greg.at.softsprocket@dot.com> - 2015-04-21 20:13 +0000
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-22 10:52 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-04-22 09:18 -0700
Re: Problems with va_list & friends... raltbos@xs4all.nl (Richard Bos) - 2015-04-21 22:25 +0000
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-23 15:59 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-23 11:51 -0700
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-23 11:26 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 16:15 -0500
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 17:23 -0400
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 13:17 -0400
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 15:26 -0500
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-20 16:15 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-21 00:42 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-22 11:15 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 21:50 +0100
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 17:04 -0400
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 08:22 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-19 18:23 +0100
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-19 13:22 -0700
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-19 21:51 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 10:01 +0100
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-20 05:08 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 11:37 +0100
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-23 20:13 -0700
Re: Problems with va_list & friends... Philipp Klaus Krause <pkk@spth.de> - 2015-04-18 09:15 +0200
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 12:13 -0700
Re: Problems with va_list & friends... Richard Damon <Richard@Damon-Family.org> - 2015-04-16 23:40 -0400
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 08:11 -0700
Page 11 of 11 — ← Prev page 1 … 9 10 [11]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2015-04-19 18:23 +0100 |
| Message-ID | <mh0o82$arf$1@dont-email.me> |
| In reply to | #60323 |
On 18/04/15 16:22, Tim Rentsch wrote:
> Richard Heathfield <rjh@cpax.org.uk> writes:
>
> [considering the wisdom of always using -Wall -Wextra -Werror]
>
>> The gcc compiler, however, is a different kettle of bananas, and
>> it does sometimes issue warnings for code that /could/ be a
>> problem in different circumstances but which I happen to know is
>> /not/ a problem in this particular case, [snip]
>
> Presumably these warnings were part of the optional diagnostics
> produced as a result of using -Wall or -Wextra (or perhaps some
> other more specialized -Wxxx option). Is that the case, or have
> you seen such unwarranted diagnostics that are produced without
> requesting any optional warning conditions? (In this regard
> I would count -pedantic in the opposite category from -Wall,
> etc.)
Yes. In the interests of scientific enquiry, I just re-built (make
clean) the module I am currently working on. Here is my CFLAGS for this
particular project:
=-W -Wall -ansi -pedantic
Here are the diagnostic messages I got:
warning: missing initialiser [-Wmissing-field-initializers] [1]
(near initialisation for 'foo.bar') [-Wmissing-field-initializers]
[1] (an interesting combination of 'ise' and 'ize' there)
Call this pair (which always occur together) A.
B: variable 'baz' set but not used [-Wunused-but-set-variable]
C: 'quux' defined but not used [-Wunused-function]
A occurs 39 times, B and C once each, in just over two thousand lines of
code.
A occurs for aggregate objects initialised using the correct idiom = {0};
B occurs in code that I haven't finished yet! The variable will be used
in due course;
C is for a static helper function that I haven't worked into the code
yet, but which will be used in due course.
B and C will eventually disappear. A is a nuisance, because I use = {0}
a lot, so I always get a small forest of these diagnostics. I'm not
about to switch them off, though, because I may well be glad of that
warning one day.
--
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 | Keith Thompson <kst-u@mib.org> |
|---|---|
| Date | 2015-04-19 13:22 -0700 |
| Message-ID | <878udnq36f.fsf@kst-u.example.com> |
| In reply to | #60440 |
Richard Heathfield <rjh@cpax.org.uk> writes:
[...]
> warning: missing initialiser [-Wmissing-field-initializers] [1]
> (near initialisation for 'foo.bar') [-Wmissing-field-initializers]
>
> [1] (an interesting combination of 'ise' and 'ize' there)
[...]
Interesting and unsurprising. Presumably the error messages are
locali[zs]ed, but command-line option names are not, since that
would break Makefiles and other build scripts.
--
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 | Robert Wessel <robertwessel2@yahoo.com> |
|---|---|
| Date | 2015-04-19 21:51 -0500 |
| Message-ID | <p2q8ja543j6r2h49kae30thlpcd2rgmoaq@4ax.com> |
| In reply to | #60440 |
On Sun, 19 Apr 2015 18:23:08 +0100, Richard Heathfield
<rjh@cpax.org.uk> wrote:
>On 18/04/15 16:22, Tim Rentsch wrote:
>> Richard Heathfield <rjh@cpax.org.uk> writes:
>>
>> [considering the wisdom of always using -Wall -Wextra -Werror]
>>
>>> The gcc compiler, however, is a different kettle of bananas, and
>>> it does sometimes issue warnings for code that /could/ be a
>>> problem in different circumstances but which I happen to know is
>>> /not/ a problem in this particular case, [snip]
>>
>> Presumably these warnings were part of the optional diagnostics
>> produced as a result of using -Wall or -Wextra (or perhaps some
>> other more specialized -Wxxx option). Is that the case, or have
>> you seen such unwarranted diagnostics that are produced without
>> requesting any optional warning conditions? (In this regard
>> I would count -pedantic in the opposite category from -Wall,
>> etc.)
>
>Yes. In the interests of scientific enquiry, I just re-built (make
>clean) the module I am currently working on. Here is my CFLAGS for this
>particular project:
>
>=-W -Wall -ansi -pedantic
>
>Here are the diagnostic messages I got:
>
>warning: missing initialiser [-Wmissing-field-initializers] [1]
>(near initialisation for 'foo.bar') [-Wmissing-field-initializers]
>
>[1] (an interesting combination of 'ise' and 'ize' there)
>
>Call this pair (which always occur together) A.
>
>B: variable 'baz' set but not used [-Wunused-but-set-variable]
>
>C: 'quux' defined but not used [-Wunused-function]
>
>A occurs 39 times, B and C once each, in just over two thousand lines of
>code.
>
>A occurs for aggregate objects initialised using the correct idiom = {0};
>
>B occurs in code that I haven't finished yet! The variable will be used
>in due course;
>
>C is for a static helper function that I haven't worked into the code
>yet, but which will be used in due course.
>
>B and C will eventually disappear. A is a nuisance, because I use = {0}
>a lot, so I always get a small forest of these diagnostics. I'm not
>about to switch them off, though, because I may well be glad of that
>warning one day.
A serious problem with that is how will you notice when the number of
type A warning increases from 39 to 40?
Perhaps the actual solution would be to turn the warnings down to the
minimum level, and always use lint, which will at least allow
consistent annotations of code to "accept" warnings once you've
reviewed them.
We do use lint, but not everywhere. And it has a pretty high pain
level for introducing on code that hasn't been developed with lint.
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2015-04-20 10:01 +0100 |
| Message-ID | <mh2f7q$lbc$1@dont-email.me> |
| In reply to | #60487 |
On 20/04/15 03:51, Robert Wessel wrote:
> On Sun, 19 Apr 2015 18:23:08 +0100, Richard Heathfield
> <rjh@cpax.org.uk> wrote:
<snip>
>>A occurs 39 times, B and C once each, in just over two thousand lines of
>>code.
>>
>>A occurs for aggregate objects initialised using the correct idiom = {0};
>>
>>B occurs in code that I haven't finished yet! The variable will be used
>>in due course;
>>
>>C is for a static helper function that I haven't worked into the code
>>yet, but which will be used in due course.
>>
>>B and C will eventually disappear. A is a nuisance, because I use = {0}
>>a lot, so I always get a small forest of these diagnostics. I'm not
>>about to switch them off, though, because I may well be glad of that
>>warning one day.
>
> A serious problem with that is how will you notice when the number of
> type A warning increases from 39 to 40?
man 1 diff
--
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 | Robert Wessel <robertwessel2@yahoo.com> |
|---|---|
| Date | 2015-04-20 05:08 -0500 |
| Message-ID | <ovj9jap3hmricpk0rjig13rb56dkv5bdr7@4ax.com> |
| In reply to | #60500 |
On Mon, 20 Apr 2015 10:01:41 +0100, Richard Heathfield
<rjh@cpax.org.uk> wrote:
>On 20/04/15 03:51, Robert Wessel wrote:
>> On Sun, 19 Apr 2015 18:23:08 +0100, Richard Heathfield
>> <rjh@cpax.org.uk> wrote:
>
><snip>
>
>>>A occurs 39 times, B and C once each, in just over two thousand lines of
>>>code.
>>>
>>>A occurs for aggregate objects initialised using the correct idiom = {0};
>>>
>>>B occurs in code that I haven't finished yet! The variable will be used
>>>in due course;
>>>
>>>C is for a static helper function that I haven't worked into the code
>>>yet, but which will be used in due course.
>>>
>>>B and C will eventually disappear. A is a nuisance, because I use = {0}
>>>a lot, so I always get a small forest of these diagnostics. I'm not
>>>about to switch them off, though, because I may well be glad of that
>>>warning one day.
>>
>> A serious problem with that is how will you notice when the number of
>> type A warning increases from 39 to 40?
>
>man 1 diff
Wouldn't a diff show changes on most builds as line numbers change?
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2015-04-20 11:37 +0100 |
| Message-ID | <mh2ks6$c4k$1@dont-email.me> |
| In reply to | #60503 |
On 20/04/15 11:08, Robert Wessel wrote:
> On Mon, 20 Apr 2015 10:01:41 +0100, Richard Heathfield
> <rjh@cpax.org.uk> wrote:
>
>>[missing initialisers warning] is a nuisance, because I use = {0}
>>>>a lot, so I always get a small forest of these diagnostics. I'm not
>>>>about to switch them off, though, because I may well be glad of that
>>>>warning one day.
>>>
>>> A serious problem with that is how will you notice when the number of
>>> type A warning increases from 39 to 40?
>>
>>man 1 diff
>
>
> Wouldn't a diff show changes on most builds as line numbers change?
Sure, but it's trivial to get a count (which shows whether you've gained
a warning of this kind), and even more trivial to know what you've just
changed.
--
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 | Tim Rentsch <txr@alumni.caltech.edu> |
|---|---|
| Date | 2015-04-23 20:13 -0700 |
| Message-ID | <kfna8xyrzez.fsf@x-alumni2.alumni.caltech.edu> |
| In reply to | #60440 |
Richard Heathfield <rjh@cpax.org.uk> writes:
> On 18/04/15 16:22, Tim Rentsch wrote:
>> Richard Heathfield <rjh@cpax.org.uk> writes:
>>
>> [considering the wisdom of always using -Wall -Wextra -Werror]
>>
>>> The gcc compiler, however, is a different kettle of bananas, and
>>> it does sometimes issue warnings for code that /could/ be a
>>> problem in different circumstances but which I happen to know is
>>> /not/ a problem in this particular case, [snip]
>>
>> Presumably these warnings were part of the optional diagnostics
>> produced as a result of using -Wall or -Wextra (or perhaps some
>> other more specialized -Wxxx option). Is that the case, or have
>> you seen such unwarranted diagnostics that are produced without
>> requesting any optional warning conditions? (In this regard I
>> would count -pedantic in the opposite category from -Wall, etc.)
>
> Yes. In the interests of scientific enquiry, I just re-built
> (make clean) the module I am currently working on. Here is my
> CFLAGS for this particular project:
>
> =-W -Wall -ansi -pedantic
>
> Here are the diagnostic messages I got:
>
> warning: missing initialiser [-Wmissing-field-initializers] [1]
> (near initialisation for 'foo.bar') [-Wmissing-field-initializers]
>
> [1] (an interesting combination of 'ise' and 'ize' there)
>
> Call this pair (which always occur together) A.
>
> B: variable 'baz' set but not used [-Wunused-but-set-variable]
>
> C: 'quux' defined but not used [-Wunused-function]
>
> A occurs 39 times, B and C once each, in just over two thousand
> lines of code.
>
> A occurs for aggregate objects initialised using the correct idiom
> = {0};
>
> B occurs in code that I haven't finished yet! The variable will
> be used in due course;
>
> C is for a static helper function that I haven't worked into the
> code yet, but which will be used in due course.
A technique for dealing with unused names (like cases B and C)
is to have a macro to eliminate the warning message, depending
on the setting of a -D option, such as (disclaimer: typed in
only)
#if SUPPRESS_UNUSED_IF_ASKED
#define OH_USE_IT_ALREADY(name) ((void) (1 ? 0 : &(name)))
#else
#define OH_USE_IT_ALREADY(name) ((void) 0) // or perhhaps nothing
#endif
...
OH_USE_IT_ALREADY( baz ); // in the function where 'baz' is
OH_USE_IT_ALREADY( quux ); // in 'quux' itself, of course
Now we can suppress individual warnings on a case-by-case basis
during normal development compiles, but make sure we haven't
overlooked any when we get to the "okay I think everything is all
set" stage.
> B and C will eventually disappear. A is a nuisance, because I use
> = {0} a lot, so I always get a small forest of these diagnostics.
> I'm not about to switch them off, though, because I may well be
> glad of that warning one day.
If confronted with having to deal with case A, as does happen from
time to time, normally I would resort to one of the following two
methods.
For structs that are function locals (presuming the type in question
has been typedef'ed to 'Foo', adjust as necessary for types without
typedef names):
extern const Foo Foo_all_zero; // in header
const Foo Foo_all_zero = { // in appropriate .c file
... zeros for all members ...
};
// at declaration, use:
Foo whatever = Foo_all_zero;
For arrays and top-level structs (similar comment about type name):
// in header
#define Foo_ALL_ZERO { ... zeros for all elements ... }
// at declaration, use:
Foo whatever = Foo_ALL_ZERO;
Obviously if we have gone to the trouble to define the
macro, the definition of Foo_all_zero can be simplified to
use the macro. We did have to write an initializer that
needs adjusting when the underlying type is changed, but
only one, which isn't too bad. This approach also can be
used for other complete values besides just all zeros, for
cases when the set of initial values is small compared to
the number of uses.
[toc] | [prev] | [next] | [standalone]
| From | Philipp Klaus Krause <pkk@spth.de> |
|---|---|
| Date | 2015-04-18 09:15 +0200 |
| Message-ID | <mgt0ba$g4n$1@solani.org> |
| In reply to | #60154 |
On 16.04.2015 19:14, Les Cargill wrote: > Philipp Klaus Krause wrote: >> On 12.04.2015 17:58, Lőrinczy Zsigmond wrote: >>> To put it simply: never compile without these flags: >>> -W -Wall -Wextra -Werror >> >> I'd rather say the opposite: >> >> Never compile with -Werror. And more important: never ship anything (be >> it tarball, snapshots, or something in your public repository) that uses >> -Werror in the build system. >> >> And I really can't see any advantage that -Werror would provide. On the >> other hand, there are lots of disadvantages: You write perfectly fine >> code today, and ship it. Tomorrow, a compiler vendor decides they don't >> like the coding style you used, and emit a warning on it. Now with >> -Werror compilation will fail for whoever wants to compile your code >> with the latest compiler version. >> I've seent his happen in GNU binutils, where it is hard o get out the >> -Werror, and where there was a time when the latest released binutils >> failed to compile with the latest released GCC due to -Werror turning a >> "Warning: right-hand operand of comma expression has no effect" into an >> error. >> >> Philipp >> > > > I'd say fix the errors produced by -Werror . > How could you have fixed warning emitted by a compiler not yet existing at the time your wrote the code? Compiler warnings depend on the opinions of those who make the compiler. This will change in the future in ways you can't predict today. I can look at the standard and write standard-compliant, good C99 code today. I can't write code today that will be considered good code by GCC 6.0. Philipp
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <txr@alumni.caltech.edu> |
|---|---|
| Date | 2015-04-18 12:13 -0700 |
| Message-ID | <kfna8y5w8pf.fsf@x-alumni2.alumni.caltech.edu> |
| In reply to | #60296 |
Philipp Klaus Krause <pkk@spth.de> writes: > On 16.04.2015 19:14, Les Cargill wrote: >> Philipp Klaus Krause wrote: >>> On 12.04.2015 17:58, L?rinczy Zsigmond wrote: >>>> To put it simply: never compile without these flags: >>>> -W -Wall -Wextra -Werror >>> >>> I'd rather say the opposite: >>> >>> Never compile with -Werror. And more important: never ship >>> anything (be it tarball, snapshots, or something in your public >>> repository) that uses -Werror in the build system. >>> >>> And I really can't see any advantage that -Werror would provide. >>> On the other hand, there are lots of disadvantages: You write >>> perfectly fine code today, and ship it. Tomorrow, a compiler >>> vendor decides they don't like the coding style you used, and emit >>> a warning on it. Now with -Werror compilation will fail for >>> whoever wants to compile your code with the latest compiler >>> version. I've seent his happen in GNU binutils, where it is hard >>> o get out the -Werror, and where there was a time when the latest >>> released binutils failed to compile with the latest released GCC >>> due to -Werror turning a "Warning: right-hand operand of comma >>> expression has no effect" into an error. >> >> I'd say fix the errors produced by -Werror . > > How could you have fixed warning emitted by a compiler not yet > existing at the time your wrote the code? > > Compiler warnings depend on the opinions of those who make the > compiler. This will change in the future in ways you can't > predict today. > > I can look at the standard and write standard-compliant, good C99 > code today. I can't write code today that will be considered good > code by GCC 6.0. In a sense that's true, but the blame for that should not be put on the compiler. Rather it should be put on the developer, who chose an *optional* compiler setting giving carte blanche to issue whatever kinds of diagnostic conditions the gcc team feels might be worth reporting. In contrast, the set of diagnostic conditions identified when gcc is run in a conforming mode (eg, -ansi or -std=c99, and -pedantic) is both stable and conservative: the conditions reported don't change too much (if at all), and the cases that do get diagnostics are pretty black and white, not fanciful. So when someone gets shot in the foot upon switching to a new version of gcc, they shouldn't blame gcc after they themselves loaded the gun and pulled the trigger. It would be different if all the exotic tests done under -Wall/-Wextra were gcc's default behavior, but they aren't, are they?
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2015-04-16 23:40 -0400 |
| Message-ID | <lg%Xw.25523$fV3.17824@fx25.iad> |
| In reply to | #60126 |
On 4/16/15 7:08 AM, Philipp Klaus Krause wrote: > On 12.04.2015 17:58, Lőrinczy Zsigmond wrote: >> To put it simply: never compile without these flags: >> -W -Wall -Wextra -Werror > > I'd rather say the opposite: > > Never compile with -Werror. And more important: never ship anything (be > it tarball, snapshots, or something in your public repository) that uses > -Werror in the build system. > > And I really can't see any advantage that -Werror would provide. On the > other hand, there are lots of disadvantages: You write perfectly fine > code today, and ship it. Tomorrow, a compiler vendor decides they don't > like the coding style you used, and emit a warning on it. Now with > -Werror compilation will fail for whoever wants to compile your code > with the latest compiler version. > I've seent his happen in GNU binutils, where it is hard o get out the > -Werror, and where there was a time when the latest released binutils > failed to compile with the latest released GCC due to -Werror turning a > "Warning: right-hand operand of comma expression has no effect" into an > error. > > Philipp > I personally don't have a problem with having an internal policy of building with -Werror especially if you have some people on the team that might be willing to let warning slide and just ignore them. I do agree that if you ship build scripts and such, that release builds should NOT include -Werror This way, should a compiler start to generate a warning that you really want to be able to just ignore (and don't have a good way to remove the warning), you can just change the policy, since it is just an INTERNAL tool.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <txr@alumni.caltech.edu> |
|---|---|
| Date | 2015-04-18 08:11 -0700 |
| Message-ID | <kfnvbgtwjxr.fsf@x-alumni2.alumni.caltech.edu> |
| In reply to | #60126 |
Philipp Klaus Krause <pkk@spth.de> writes:
> On 12.04.2015 17:58, L?rinczy Zsigmond wrote:
>> To put it simply: never compile without these flags:
>> -W -Wall -Wextra -Werror
>
> I'd rather say the opposite:
>
> Never compile with -Werror. And more important: never ship
> anything (be it tarball, snapshots, or something in your public
> repository) that uses -Werror in the build system.
I will advocate an opposing viewpoint. *Always* use -Werror (and
also -pedantic), and ship that way. *Sometimes* compile with -W
(aka -Wextra) or -Wall, or both, and clean out the cruft. But
always use -Werror.
> And I really can't see any advantage that -Werror would provide.
The advantage of using -Werror is to force you (or other
developers not as enlightened) to fix problems, because for
better or worse gcc often takes a rather lax view of what
constitutes an "error" - some clearcut violations get only
warnings, unless -Werror is used. And, rather sadly, IME it is
true too often that developers (yes, even the best of them) will
not correct such situations unless forced.
> On the other hand, there are lots of disadvantages: You write
> perfectly fine code today, and ship it. Tomorrow, a compiler
> vendor decides they don't like the coding style you used, and emit
> a warning on it. Now with -Werror compilation will fail for
> whoever wants to compile your code with the latest compiler
> version.
>
> I've seent his happen in GNU binutils, where it is hard o get out
> the -Werror, and where there was a time when the latest released
> binutils failed to compile with the latest released GCC due to
> -Werror turning a "Warning: right-hand operand of comma expression
> has no effect" into an error.
The problem is not -Werror but -W/-Wextra and -Wall. These
options have the following problems (list not necessarily
exhaustive):
* whether/which conditions are detected depends on choice
of optimization level;
* some of the "errors" (or "warnings", if you like) are
purely style advisories, and not always good ones;
* some offending "problems" can be "fixed" by writing
code that is obviously semantically identical (which
indicates some kind of bad reasoning somewhere);
* some tested conditions generate too many false positives
(the problem being not that there are false positives,
which are unavoidable, but that there isn't more effort
put in to reduce them);
* AFAIK there are no corresponding false negatives, but I
am not sure of that - relying on gcc's detection to find
such problems may lead to a false sense of security; and
* whether/which conditions are detected depends on which
version of gcc is used, which as you point out means the
diagnostics we get today may not match the diagnostics we
get tomorrow. In contrast, the diagnostics we get with
-Werror alone (again assuming -pedantic) are IME quite
stable, and also almost without exception indicate a
serious violation. (I do know of one counter-example to
that, but only one.)
I do find it helpful to turn on -Wall/-Wextra from time to
time, and go through the list looking for problems. But not
all the time, largely because of the version drift problem.
The underlying cause is the philosophy about what these options
should mean, which is more akin to -Wbox-of-chocolates (because
you never know what you're going to get). If the conditions
being checked were stable, then always using -Wall/-Wextra
would be a viable policy. The problem is they aren't.
[toc] | [prev] | [standalone]
Page 11 of 11 — ← Prev page 1 … 9 10 [11]
Back to top | Article view | comp.lang.c
csiph-web