Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #60841 > unrolled thread
| Started by | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| First post | 2015-04-23 08:09 +0100 |
| Last post | 2015-04-25 04:01 -0700 |
| Articles | 20 on this page of 432 — 38 participants |
Back to article view | Back to comp.lang.c
Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 08:09 +0100
Re: Spurious diagnostic messages Noob <root@127.0.0.1> - 2015-04-23 10:56 +0200
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-04-23 21:13 +1200
Re: Spurious diagnostic messages Noob <root@127.0.0.1> - 2015-04-23 11:25 +0200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 10:36 +0100
Re: Spurious diagnostic messages Noob <root@127.0.0.1> - 2015-04-23 11:54 +0200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 11:06 +0100
Re: Spurious diagnostic messages Noob <root@127.0.0.1> - 2015-04-23 12:35 +0200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 11:44 +0100
Re: Spurious diagnostic messages Noob <root@127.0.0.1> - 2015-04-23 12:56 +0200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 12:16 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-04-23 12:09 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-04-24 07:52 +1200
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-04-23 16:15 -0400
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-04-24 08:21 +1200
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-04-23 16:44 -0400
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-04-24 13:01 +0200
Re: Spurious diagnostic messages gwowen <gwowen@gmail.com> - 2015-04-23 04:16 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 12:19 +0100
Re: Spurious diagnostic messages Robbie Hatley <see.my.sig@for.my.address> - 2015-04-24 04:42 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-24 16:07 +0100
Re: Spurious diagnostic messages Robbie Hatley <see.my.sig@for.my.address> - 2015-04-25 22:08 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-26 14:29 +0100
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-04-26 15:45 +0000
Re: Spurious diagnostic messages Ben Bacarisse <ben.lists@bsb.me.uk> - 2015-04-23 11:43 +0100
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-23 09:29 +0000
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-04-23 11:52 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-25 03:03 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 10:53 +0100
Re: Spurious diagnostic messages Ben Bacarisse <ben.lists@bsb.me.uk> - 2015-04-23 11:37 +0100
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 12:12 +0100
Re: Spurious diagnostic messages Noob <root@127.0.0.1> - 2015-04-23 12:46 +0200
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-04-23 08:47 -0400
Re: Spurious diagnostic messages Fred K <fred.l.kleinschmidt@gmail.com> - 2015-04-23 07:39 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-23 16:20 +0100
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-04-23 12:43 -0400
Re: Spurious diagnostic messages James Dow Allen <jdallen2000@yahoo.com> - 2015-04-24 01:40 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-24 11:14 +0100
Re: Spurious diagnostic messages James Dow Allen <jdallen2000@yahoo.com> - 2015-04-24 10:02 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-24 18:20 +0100
Re: Spurious diagnostic messages James Dow Allen <jdallen2000@yahoo.com> - 2015-04-24 13:27 -0700
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-04-25 10:25 +0000
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-04-24 23:02 +0100
Re: Spurious diagnostic messages Ben Bacarisse <ben.lists@bsb.me.uk> - 2015-04-24 11:30 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-26 08:09 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-04-26 12:26 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-28 09:52 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-04-28 11:27 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-28 20:09 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-30 07:11 -0700
Re: Spurious diagnostic messages Phil Carmody <pc+usenet@asdf.org> - 2015-05-09 13:14 +0300
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-10 08:23 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-10 11:06 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-11 21:52 -0700
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-05-10 12:20 -0400
Re: Spurious diagnostic messages Richard Damon <Richard@Damon-Family.org> - 2015-05-10 13:22 -0400
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-10 18:44 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-10 11:12 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-11 21:46 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-12 10:11 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-12 18:26 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-12 11:29 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-13 09:14 +0200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-13 11:55 +0100
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-13 14:55 +0200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-13 14:35 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-13 08:24 -0700
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-13 18:47 -0500
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-13 21:15 +0200
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-13 19:40 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-13 21:08 +0100
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-13 20:52 +0000
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-05-13 21:06 +0000
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-13 23:28 +0000
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-05-14 00:19 +0000
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-14 04:29 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-14 09:57 +0100
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-14 04:56 -0500
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-14 11:34 +0100
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-14 17:24 +0000
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-16 01:21 -0500
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-17 10:00 +0100
Re: Spurious diagnostic messages David Thompson <dave.thompson2@verizon.net> - 2015-06-21 12:46 -0400
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-06-21 13:20 -0400
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-14 17:22 +0000
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-16 01:59 -0500
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-16 09:51 +0000
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-16 05:36 -0500
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-16 19:32 +0000
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-14 17:13 +0000
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-05-17 10:13 +0000
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-13 18:54 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-14 01:31 +0100
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-13 21:05 -0500
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-14 00:48 -0500
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-14 17:27 +0000
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-16 02:00 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-14 09:41 +0100
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-14 05:02 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-14 13:44 +0100
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-14 17:32 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-14 20:18 +0100
Re: Spurious diagnostic messages Öö Tiib <ootiib@hot.ee> - 2015-05-15 05:32 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-15 13:47 -0500
Re: Spurious diagnostic messages Öö Tiib <ootiib@hot.ee> - 2015-05-16 02:51 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-16 17:13 -0500
Re: Spurious diagnostic messages Öö Tiib <ootiib@hot.ee> - 2015-05-17 22:34 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-20 08:47 -0700
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-05-17 10:36 +0000
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-05-17 12:26 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-17 14:13 +0100
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-05-17 13:45 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-17 15:02 +0100
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-05-17 14:20 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-17 15:51 +0100
I'm starting a new thread (Was: Spurious diagnostic messages) gazelle@shell.xmission.com (Kenny McCormack) - 2015-05-17 15:00 +0000
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-17 07:58 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-17 15:36 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-17 22:28 +0100
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-20 08:59 -0700
Re: Spurious diagnostic messages Les Cargill <lcargill99@comcast.com> - 2015-05-20 11:58 -0500
Re: Spurious diagnostic messages bart4858@gmail.com - 2015-05-20 14:00 -0700
Re: Spurious diagnostic messages Les Cargill <lcargill99@comcast.com> - 2015-05-20 18:10 -0500
Re: Spurious diagnostic messages bart4858@gmail.com - 2015-05-21 00:57 -0700
Re: Spurious diagnostic messages Les Cargill <lcargill99@comcast.com> - 2015-05-21 12:40 -0500
Re: Spurious diagnostic messages bart4858@gmail.com - 2015-05-21 13:25 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-21 14:33 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-22 09:11 +0200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-22 08:15 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-22 11:47 -0500
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-22 12:11 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-05-23 07:26 +1200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-22 14:14 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-05-23 09:28 +1200
Re: Spurious diagnostic messages Les Cargill <lcargill99@comcast.com> - 2015-05-22 21:36 -0500
Re: Spurious diagnostic messages Phil Carmody <pc+usenet@asdf.org> - 2015-05-25 11:36 +0300
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-22 14:16 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-22 08:38 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-22 18:06 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-22 13:56 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-22 23:38 +0100
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-22 18:28 -0500
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-22 16:44 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-24 07:44 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-24 16:52 +0100
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-05-24 22:19 +0100
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-24 22:28 +0100
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-05-25 00:00 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-10 10:12 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-24 23:13 +0100
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-25 11:30 +0100
Re: Spurious diagnostic messages Öö Tiib <ootiib@hot.ee> - 2015-05-25 07:41 -0700
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-05-25 17:10 +0100
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-25 17:42 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-25 12:20 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-10 10:07 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-10 20:09 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-11 11:19 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-11 20:25 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-16 08:48 -0700
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-07-16 14:21 -0500
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-20 08:52 -0700
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-07-20 21:21 +0000
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-23 02:49 -0700
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-07-23 21:35 +0000
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-27 07:30 -0700
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-07-24 15:35 -0500
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-27 08:13 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-27 18:14 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-01 09:06 -0700
Re: Spurious diagnostic messages "Bartc" <bartc@freeuk.com> - 2015-08-01 18:26 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-09 08:45 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-23 11:48 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-27 08:50 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-17 11:49 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-20 09:06 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-20 18:18 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-07-20 11:52 -0700
Re: Spurious diagnostic messages Gareth Owen <gwowen@gmail.com> - 2015-07-20 20:09 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-07-20 13:18 -0700
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-07-20 16:24 -0400
Re: Spurious diagnostic messages Gareth Owen <gwowen@gmail.com> - 2015-07-21 07:59 +0100
Re: Spurious diagnostic messages Richard Damon <Richard@Damon-Family.org> - 2015-07-21 21:07 -0400
Re: Spurious diagnostic messages Gareth Owen <gwowen@gmail.com> - 2015-07-21 07:52 +0100
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-20 23:17 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-07-20 15:51 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-24 13:50 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-24 22:45 +0100
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-07-25 18:59 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-25 20:49 +0100
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-07-31 13:22 +0000
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-27 08:48 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-25 12:04 +0200
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-05-26 09:11 +0000
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-26 11:26 +0200
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-05-26 22:02 +1200
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-05-26 14:59 +0100
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-26 16:58 +0200
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-26 16:19 +0100
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-27 08:45 +0200
Re: Spurious diagnostic messages David Thompson <dave.thompson2@verizon.net> - 2015-06-21 12:46 -0400
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-06-21 20:41 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-06-21 13:27 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-10 10:19 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-07-11 08:47 +1200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-11 13:40 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-07-21 13:49 +0200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-25 20:17 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-07-26 16:54 +1200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-31 01:25 -0700
Re: Spurious diagnostic messages David Kleinecke <dkleinecke@gmail.com> - 2015-07-31 17:46 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-02 06:00 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-08-02 16:31 +0200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-24 13:13 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-08-25 08:36 +1200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-07-31 09:01 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-08-01 08:13 +1200
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-08-02 01:08 -0500
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-02 14:29 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-08-03 09:15 +1200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-03 08:22 -0700
Re: Spurious diagnostic messages Rosario19 <Ros@invalid.invalid> - 2015-08-22 08:24 +0200
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-08-22 19:24 +1200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-24 11:02 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-08-24 20:13 +0100
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-08-30 13:30 +0000
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-08-25 08:12 +1200
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-08-02 16:56 -0500
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-03 08:36 -0700
Re: Spurious diagnostic messages David Kleinecke <dkleinecke@gmail.com> - 2015-08-03 17:32 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-03 18:41 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-24 11:04 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-26 11:08 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-07-26 15:35 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-07-27 00:17 +0100
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-07-27 00:53 +0000
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-07-27 08:19 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-01 10:10 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-01 13:43 -0700
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-08-02 00:04 +0100
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-08-02 01:16 -0500
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-08-02 12:21 +0100
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-08-02 19:42 +0200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-24 09:58 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-08-24 22:22 +0200
Re: Spurious diagnostic messages Richard Damon <Richard@Damon-Family.org> - 2015-08-01 20:20 -0400
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-02 18:57 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-08-02 08:21 +1200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-01 14:31 -0700
Re: Spurious diagnostic messages Tonton Th <tTh@nowhere.invalid> - 2015-08-01 22:26 +0000
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-08-02 01:10 -0500
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-08-02 09:02 -0400
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-08-02 14:23 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-02 15:31 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-02 09:01 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-02 16:56 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-03 10:18 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-08-03 12:10 +1200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-24 10:52 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-08-24 20:01 +0100
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-08-25 08:16 +1200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-08-03 14:11 +0100
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-08-04 10:56 +0000
Re: Spurious diagnostic messages David Kleinecke <dkleinecke@gmail.com> - 2015-08-01 16:52 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-08-02 12:59 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-09 13:39 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-08-02 13:37 +0200
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-08-02 13:17 +0100
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-08-02 19:45 +0200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-02 15:52 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-08-03 09:34 +0200
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-08-04 11:04 +0000
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-04 09:07 -0700
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-08-09 13:28 +0000
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-08-02 14:00 -0500
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-09-05 11:31 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-09-06 10:47 +0200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-09-06 13:27 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-02 15:53 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-02 15:45 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-08-03 09:40 +0200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-08-24 11:41 -0700
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-08-04 11:23 +0000
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-08-04 09:12 -0700
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-08-09 13:33 +0000
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-09-06 10:59 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-09-06 22:21 +0100
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-09-07 13:44 +1200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-20 10:44 -0700
Re: Spurious diagnostic messages bart4858@gmail.com - 2015-05-20 13:42 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-20 14:17 -0700
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-05-20 21:25 +0000
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-05-23 10:17 +0000
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-05-23 10:15 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-23 11:46 +0100
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-05-23 17:22 +0100
Re: Spurious diagnostic messages Phil Carmody <pc+usenet@asdf.org> - 2015-05-25 11:49 +0300
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-05-25 10:50 +0100
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-23 15:57 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-23 22:51 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-23 19:01 -0700
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-23 22:50 -0500
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-23 23:41 -0500
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-24 00:40 -0500
Re: Spurious diagnostic messages asetofsymbols@gmail.com - 2015-05-24 02:57 -0700
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-24 07:40 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-24 14:24 +0100
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-24 09:23 -0500
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-24 15:36 +0100
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-05-24 13:10 -0400
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-24 07:44 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-24 19:26 -0500
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-25 00:51 -0500
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-25 15:48 -0500
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-26 02:36 -0500
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-26 13:23 -0500
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-05-27 00:55 +0100
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-05-29 12:28 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-29 13:44 +0100
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-05-29 15:55 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-29 18:17 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-29 10:52 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-26 13:27 -0500
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-26 21:09 -0500
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-27 00:03 -0500
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-27 00:59 -0500
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-27 01:15 -0500
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-05-27 13:34 -0400
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-27 14:07 -0500
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-27 19:53 +0000
Re: Spurious diagnostic messages Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-05-27 21:21 +0100
Re: Spurious diagnostic messages luser droog <luser.droog@gmail.com> - 2015-05-27 21:45 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-28 17:36 -0500
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-05-27 10:36 -0400
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-27 16:54 +0200
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-27 16:08 +0100
Re: Spurious diagnostic messages Les Cargill <lcargill99@comcast.com> - 2015-05-27 12:18 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-27 18:39 +0100
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-27 22:04 +0200
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-27 21:38 +0100
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-27 19:54 -0500
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-27 19:58 -0500
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-28 14:24 +0200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-27 13:51 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-10 11:08 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-10 11:05 -0700
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-07-10 18:08 +0000
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-11 07:55 -0700
Re: Spurious diagnostic messages gazelle@shell.xmission.com (Kenny McCormack) - 2015-07-11 15:02 +0000
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-07-21 14:08 +0200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-07-21 13:27 +0100
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-07-21 15:30 +0200
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-07-22 15:04 +0000
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-25 10:27 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-07-21 13:55 +0200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-07-25 14:18 -0700
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-08-02 20:16 +0200
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-09-06 09:49 -0700
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-27 22:20 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-28 10:28 +0100
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-28 06:00 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-27 10:22 +0100
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-27 10:32 -0500
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-27 17:08 +0100
Re: Spurious diagnostic messages Thomas Jahns <jahns@idontlikespam.dkrz.de> - 2015-05-28 15:49 +0200
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-28 15:03 +0100
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-05-28 14:35 -0400
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-28 16:54 +0100
Re: Spurious diagnostic messages jadill33@gmail.com - 2015-05-28 10:32 -0700
Re: Spurious diagnostic messages Thomas Jahns <jahns@idontlikespam.dkrz.de> - 2015-05-29 10:17 +0200
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-27 10:40 -0700
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-27 19:56 +0000
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-27 13:46 -0700
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-27 21:16 +0000
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-27 15:47 -0500
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-27 14:08 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-27 22:11 +0100
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-27 20:10 -0500
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-05-28 02:21 +0100
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-28 03:21 +0000
Re: Spurious diagnostic messages luser droog <luser.droog@gmail.com> - 2015-05-27 22:17 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-27 22:22 +0100
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-28 14:52 +0200
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-27 18:55 +0100
Re: Spurious diagnostic messages Morris Dovey <mrdovey@iedu.com> - 2015-05-27 15:31 -0500
Re: Spurious diagnostic messages Phil Carmody <pc+usenet@asdf.org> - 2015-05-25 12:11 +0300
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-25 11:04 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-25 12:30 -0700
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-25 15:41 -0500
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-25 15:20 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-24 10:57 +0100
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-25 14:31 -0500
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-25 22:30 +0100
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-25 17:56 -0500
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-05-29 12:34 +0000
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-29 14:04 +0100
Re: Spurious diagnostic messages Alain Ketterlin <alain@universite-de-strasbourg.fr.invalid> - 2015-05-29 15:28 +0200
Re: Spurious diagnostic messages raltbos@xs4all.nl (Richard Bos) - 2015-06-05 15:18 +0000
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-29 15:31 +0200
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-17 15:35 -0500
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-17 07:56 -0700
Re: Spurious diagnostic messages Bartc <bc@freeuk.com> - 2015-05-17 16:14 +0100
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-17 12:57 -0700
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-17 15:46 +0000
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-05-18 11:10 -0400
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-18 08:56 -0700
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-18 18:09 +0000
Re: Spurious diagnostic messages glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-05-18 18:03 +0000
Re: Spurious diagnostic messages James Kuyper <jameskuyper@verizon.net> - 2015-05-18 14:41 -0400
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-17 15:39 -0500
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-17 13:58 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-13 19:17 -0700
Re: Spurious diagnostic messages Nathan Wagner <nw@hydaspes.if.org> - 2015-05-14 09:54 +0000
Re: Spurious diagnostic messages Stephen Sprunk <stephen@sprunk.org> - 2015-05-14 08:57 -0500
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-14 08:31 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-14 08:33 -0700
Re: Spurious diagnostic messages Ian Collins <ian-news@hotmail.com> - 2015-05-14 14:37 +1200
Re: Spurious diagnostic messages David Brown <david.brown@hesbynett.no> - 2015-05-14 13:13 +0200
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-15 16:26 -0500
Re: Spurious diagnostic messages Robert Wessel <robertwessel2@yahoo.com> - 2015-05-13 18:44 -0500
Re: Spurious diagnostic messages David Thompson <dave.thompson2@verizon.net> - 2015-06-21 12:46 -0400
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-22 07:37 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-12 11:23 -0700
Re: Spurious diagnostic messages Keith Thompson <kst-u@mib.org> - 2015-05-12 13:08 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-22 06:32 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-28 12:30 -0700
Re: Spurious diagnostic messages James Dow Allen <gmail@jamesdowallen.nospam> - 2015-04-29 04:07 +0000
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-30 07:48 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-25 03:32 -0700
Re: Spurious diagnostic messages Richard Heathfield <rjh@cpax.org.uk> - 2015-04-26 09:33 +0100
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-26 07:37 -0700
Re: Spurious diagnostic messages Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-25 04:01 -0700
Page 16 of 22 — ← Prev page 1 … 14 15 [16] 17 18 … 22 Next page →
| From | Keith Thompson <kst-u@mib.org> |
|---|---|
| Date | 2015-05-23 19:01 -0700 |
| Message-ID | <871ti6rawv.fsf@kst-u.example.com> |
| In reply to | #62505 |
Bartc <bc@freeuk.com> writes:
[...]
> My point is that A-Z is the de-facto standard, just as the 8-bit byte
> is, and as the ASCII coding is for that basic alphabet.
A-Z is the de facto standard for what exactly?
Most methods of transmitting and storing text these days allow for
Unicode, typically using either UTF-8 or UTF-16 (the latter is mostly
used on MS Windows). You were able to include an é in your recent
followup, and I was able to read it on my screen. And there are other
ways of encoding non-ASCII characters (see HTML for example).
Sure, the ways of *entering* non-ASCII characters are varied and often
awkward; that's the price we pay for not having a million or so keys on
our keyboards. Written languages were designed for pens, brushes, or
styluses; entering text by pressing buttons is a more recent and
imperfect innovation.
And ASCII is not universal; IBM mainframes using EBCDIC still exist.
You're free to ignore them; not everyone has that freedom.
[...]
--
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-05-23 22:50 -0500 |
| Message-ID | <3qh2ma1vojvb0add103h8tabbcb5gedhhb@4ax.com> |
| In reply to | #62508 |
On Sat, 23 May 2015 19:01:36 -0700, Keith Thompson <kst-u@mib.org> wrote: >Bartc <bc@freeuk.com> writes: >[...] >> My point is that A-Z is the de-facto standard, just as the 8-bit byte >> is, and as the ASCII coding is for that basic alphabet. > >A-Z is the de facto standard for what exactly? > >Most methods of transmitting and storing text these days allow for >Unicode, typically using either UTF-8 or UTF-16 (the latter is mostly >used on MS Windows). You were able to include an é in your recent >followup, and I was able to read it on my screen. And there are other >ways of encoding non-ASCII characters (see HTML for example). > >Sure, the ways of *entering* non-ASCII characters are varied and often >awkward; that's the price we pay for not having a million or so keys on >our keyboards. Written languages were designed for pens, brushes, or >styluses; entering text by pressing buttons is a more recent and >imperfect innovation. > >And ASCII is not universal; IBM mainframes using EBCDIC still exist. >You're free to ignore them; not everyone has that freedom. Just to get the conversation back on track (I think)... I believe the subject was an extended form of the case label where you could specify something like: case 3..7: to represent the equivalent of: case 3: case 4: case 5: case 6: case 7: I think we're all agreed that is clear enough, and has at least some use cases (although not whether it's sufficiently useful to include in the language). The problem comes up when the specification is: case 'A'..'Z': In C, of course, those character literals are numbers, and what numbers they are depends on the implementation, but what the above means is obvious assuming the standard handling of character literals. That the above would have different results on an ASCII and EBCDIC machines, is a slightly different issue. As has been pointed out, the same problem exists if you were to code a character test as: if (c >= 'a' && c <= 'z') Personally I find the use case for a simple range compelling enough, and the issue with collating sequence small enough, that I'd like the simple extension in the language. YMMV. Bartc appears to be proposing special handling of some forms of the range, specifically so that the above case would result in matches for the 26 basic letters. A major issue is exactly what the syntax and semantics of that would be. For example, what heppens when the following are specified: case 'A'+2..'J'+2: case 'A'..'b': case '['..']': I don't see any solutions that aren't particularly ugly. So there's probably no way, in C, to actually do that.
[toc] | [prev] | [next] | [standalone]
| From | Morris Dovey <mrdovey@iedu.com> |
|---|---|
| Date | 2015-05-23 23:41 -0500 |
| Message-ID | <mjrkov$9hl$1@speranza.aioe.org> |
| In reply to | #62511 |
On 5/23/15 10:50 PM, Robert Wessel wrote:
> The problem comes up when the specification is:
>
> case 'A'..'Z':
>
> In C, of course, those character literals are numbers, and what
> numbers they are depends on the implementation, but what the above
> means is obvious assuming the standard handling of character literals.
> That the above would have different results on an ASCII and EBCDIC
> machines, is a slightly different issue. As has been pointed out, the
> same problem exists if you were to code a character test as:
>
> if (c >= 'a' && c <= 'z')
>
> Personally I find the use case for a simple range compelling enough,
> and the issue with collating sequence small enough, that I'd like the
> simple extension in the language. YMMV.
I’d kinda like to see:
case 'A'..'Ω':
too. :-)
--
Morris Dovey
http://www.iedu.com/Solar
[toc] | [prev] | [next] | [standalone]
| From | Stephen Sprunk <stephen@sprunk.org> |
|---|---|
| Date | 2015-05-24 00:40 -0500 |
| Message-ID | <mjro5b$26o$1@dont-email.me> |
| In reply to | #62513 |
On 23-May-15 23:41, Morris Dovey wrote: > On 5/23/15 10:50 PM, Robert Wessel wrote: >> The problem comes up when the specification is: >> >> case 'A'..'Z': >> >> ... > > I’d kinda like to see: > > case 'A'..'Ω': > > too. :-) Even if we assume you're switching on a wchar_t (or a UTF-8 string, if that were to be allowed too), that probably won't do what you expect: http://unicode.org/charts/PDF/U0370.pdf Internationalization is hard; let's go shopping! S -- Stephen Sprunk "God does not play dice." --Albert Einstein CCIE #3723 "God is an inveterate gambler, and He throws the K5SSS dice at every possible opportunity." --Stephen Hawking
[toc] | [prev] | [next] | [standalone]
| From | asetofsymbols@gmail.com |
|---|---|
| Date | 2015-05-24 02:57 -0700 |
| Message-ID | <b8fdf9d0-7c2c-4ebb-8988-92dd958c270f@googlegroups.com> |
| In reply to | #62514 |
If a Language is written with
256 char...
One can use permutations
P:{0..256}->{0..256}
instead of switch
If one language is different of
asci in disposition of char
if x is a char in above disposition
P(x)
would be the ascii char correspond
to x
[toc] | [prev] | [next] | [standalone]
| From | Morris Dovey <mrdovey@iedu.com> |
|---|---|
| Date | 2015-05-24 07:40 -0500 |
| Message-ID | <mjsgr4$36c$1@speranza.aioe.org> |
| In reply to | #62514 |
On 5/24/15 12:40 AM, Stephen Sprunk wrote:
> On 23-May-15 23:41, Morris Dovey wrote:
>> On 5/23/15 10:50 PM, Robert Wessel wrote:
>>> The problem comes up when the specification is:
>>>
>>> case 'A'..'Z':
>>>
>>> ...
>>
>> I’d kinda like to see:
>>
>> case 'A'..'Ω':
>>
>> too. :-)
>
> Even if we assume you're switching on a wchar_t (or a UTF-8 string, if
> that were to be allowed too), that probably won't do what you expect:
>
> http://unicode.org/charts/PDF/U0370.pdf
>
> Internationalization is hard; let's go shopping!
I was being (somewhat) facetious. I think the problem has been poorly
stated, because it does not allow distinction between the numerical
value of a character and a collating sequence. Consider
collate("0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ");
case co('A')..co('F'):
where co(x) returns the subscript of x within the specified collating
sequence, independent of the character encoding - and there's no reason
not to make a wchar_t version.
This kind of approach could resolve ASCII/EBCDIC/? encoding headaches
and (perhaps) make some parts of internationalization easier.
Having said all that, I’ll add that I get along quite well without
ranges, TYVM.
--
Morris Dovey
http://www.iedu.com/Solar
[toc] | [prev] | [next] | [standalone]
| From | Bartc <bc@freeuk.com> |
|---|---|
| Date | 2015-05-24 14:24 +0100 |
| Message-ID | <mjsjci$p6c$1@dont-email.me> |
| In reply to | #62521 |
On 24/05/2015 13:40, Morris Dovey wrote:
> On 5/24/15 12:40 AM, Stephen Sprunk wrote:
>> On 23-May-15 23:41, Morris Dovey wrote:
>>> I’d kinda like to see:
>>>
>>> case 'A'..'Ω':
>>>
>>> too. :-)
>>
>> Even if we assume you're switching on a wchar_t (or a UTF-8 string, if
>> that were to be allowed too), that probably won't do what you expect:
>>
>> http://unicode.org/charts/PDF/U0370.pdf
>>
>> Internationalization is hard; let's go shopping!
>
> I was being (somewhat) facetious. I think the problem has been poorly
> stated, because it does not allow distinction between the numerical
> value of a character and a collating sequence. Consider
>
> collate("0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ");
>
> case co('A')..co('F'):
>
> where co(x) returns the subscript of x within the specified collating
> sequence, independent of the character encoding - and there's no reason
> not to make a wchar_t version.
>
> This kind of approach could resolve ASCII/EBCDIC/? encoding headaches
> and (perhaps) make some parts of internationalization easier.
Yes, or just ascii('A'), since the sort of people who code such ranges
will usually have ASCII in mind.
And of course ascii() will be a no-op on most compilers. On the EBCDIC
ones, it could just generate an error, or map to ebcdic_to_ascii[].
It also solve the problem of 'A'+2 by writing it as co('A')+2 (with
perhaps an inverse operation available).
However, this would still require ranges, which are harder to add tidily
when they are not built-in.
--
Bartc
[toc] | [prev] | [next] | [standalone]
| From | Morris Dovey <mrdovey@iedu.com> |
|---|---|
| Date | 2015-05-24 09:23 -0500 |
| Message-ID | <mjsmt1$gmq$1@speranza.aioe.org> |
| In reply to | #62522 |
On 5/24/15 8:24 AM, Bartc wrote:
> On 24/05/2015 13:40, Morris Dovey wrote:
>> On 5/24/15 12:40 AM, Stephen Sprunk wrote:
>>> On 23-May-15 23:41, Morris Dovey wrote:
>
>>>> I’d kinda like to see:
>>>>
>>>> case 'A'..'Ω':
>>>>
>>>> too. :-)
>>>
>>> Even if we assume you're switching on a wchar_t (or a UTF-8 string, if
>>> that were to be allowed too), that probably won't do what you expect:
>>>
>>> http://unicode.org/charts/PDF/U0370.pdf
>>>
>>> Internationalization is hard; let's go shopping!
>>
>> I was being (somewhat) facetious. I think the problem has been poorly
>> stated, because it does not allow distinction between the numerical
>> value of a character and a collating sequence. Consider
>>
>> collate("0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ");
>>
>> case co('A')..co('F'):
>>
>> where co(x) returns the subscript of x within the specified collating
>> sequence, independent of the character encoding - and there's no reason
>> not to make a wchar_t version.
>>
>> This kind of approach could resolve ASCII/EBCDIC/? encoding headaches
>> and (perhaps) make some parts of internationalization easier.
>
> Yes, or just ascii('A'), since the sort of people who code such ranges
> will usually have ASCII in mind.
>
> And of course ascii() will be a no-op on most compilers. On the EBCDIC
> ones, it could just generate an error, or map to ebcdic_to_ascii[].
>
> It also solve the problem of 'A'+2 by writing it as co('A')+2 (with
> perhaps an inverse operation available).
>
> However, this would still require ranges, which are harder to add tidily
> when they are not built-in.
They're easy enough, but assuming English/ASCII is rather parochial in a
programming language with an /international/ standard - in a world where
only 5.4% of people are native English speakers.
https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers
If it's worth doing, it's worth doing right - and if it's not worth
doing right, then it's not worth doing.
--
Morris Dovey
http://www.iedu.com/Solar
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2015-05-24 15:36 +0100 |
| Message-ID | <mjsniq$9v2$1@dont-email.me> |
| In reply to | #62524 |
On 24/05/15 15:23, Morris Dovey wrote: <snip> > > [...] assuming English/ASCII is rather parochial in a > programming language with an /international/ standard - in a world where > only 5.4% of people are native English speakers. > > https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers > > If it's worth doing, it's worth doing right - and if it's not worth > doing right, then it's not worth doing. If you're saying it's worth learning English to get the percentage up a bit (say, for instance, to about 100%), I'd have to agree with you. -- 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 | James Kuyper <jameskuyper@verizon.net> |
|---|---|
| Date | 2015-05-24 13:10 -0400 |
| Message-ID | <mjt0j9$c2v$1@dont-email.me> |
| In reply to | #62524 |
On 05/24/2015 10:23 AM, Morris Dovey wrote: ... > They're easy enough, but assuming English/ASCII is rather parochial in a > programming language with an /international/ standard - in a world where > only 5.4% of people are native English speakers. > > https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers Keep in mind, however, that C originated in the US. Despite the fact that it's an international standard, I believe that it's officially published only in English. I would expect that the committee's official meetings are conducted almost entirely in English - can anyone who's actually attended those meeting confirm that guess? All of C's keywords, and all of the identifiers that provide the interface to the C standard library, are either actual English words, or are clearly derived from English. I get the impression that even the C users who are not native speakers of English, are disproportionately likely to be able to at least read English, even if they are horrible at writing it. I'm all in favor of internationalization - but C is far from being the ideal starting point for a completely internationalized programming language. > If it's worth doing, it's worth doing right - and if it's not worth > doing right, then it's not worth doing. I've frequently heard this claim, but it makes no sense to me. In general, there's no unique right way to do something, just a variety of different ways to do it better or worse, with corresponding costs. There's a way of doing any particular thing that maximizes the value of the results minus the values of the associated costs, and that's the best way to do it. Doing the job any better than that is a waste of valuable resources that could be better spent on some other task. Example: at a time when I was in charge of a grand total of 1.5 subordinates, my group was asked to spend a lot time writing up detailed descriptions of the procedures we used to develop our software. The goal was to get us officially certified as having met a certain level of sophistication in our development practices. I strongly approve of the general idea, but the specific requirements we were asked to meet were designed for a group that is large enough to justify hiring a full-time person who's only job was to monitor conformance with those procedures. They were ridiculously excessive for a group of our size. I don't mean that the development procedures were too onerous - that would not have been a problem - the procedures we actually currently use would have been good enough. It was the requirement that we determine what our procedures should be, write them up in detail, get then approved, and then periodically review them for appropriateness. At the required level of detail, that would have kept me (the only person in my group sufficiently fluent in English to do the job) busy for several years. That was overkill for a group of our size - but according to someone, doing things that way was "doing it right". -- James Kuyper
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <txr@alumni.caltech.edu> |
|---|---|
| Date | 2015-05-24 07:44 -0700 |
| Message-ID | <kfnr3q66nmc.fsf@x-alumni2.alumni.caltech.edu> |
| In reply to | #62521 |
Morris Dovey <mrdovey@iedu.com> writes: > [snip] > Having said all that, I'll add that I get along quite well without > ranges, TYVM. +1
[toc] | [prev] | [next] | [standalone]
| From | Stephen Sprunk <stephen@sprunk.org> |
|---|---|
| Date | 2015-05-24 19:26 -0500 |
| Message-ID | <mjtq6b$7e6$1@dont-email.me> |
| In reply to | #62521 |
On 24-May-15 07:40, Morris Dovey wrote:
> On 5/24/15 12:40 AM, Stephen Sprunk wrote:
>> On 23-May-15 23:41, Morris Dovey wrote:
>>> I’d kinda like to see:
>>>
>>> case 'A'..'Ω':
>>>
>>> too. :-)
>>
>> Even if we assume you're switching on a wchar_t (or a UTF-8 string,
>> if that were to be allowed too), that probably won't do what you
>> expect:
>>
>> http://unicode.org/charts/PDF/U0370.pdf
>>
>> Internationalization is hard; let's go shopping!
>
> I was being (somewhat) facetious. I think the problem has been
> poorly stated, because it does not allow distinction between the
> numerical value of a character and a collating sequence. Consider
>
> collate("0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ");
>
> case co('A')..co('F'):
>
> where co(x) returns the subscript of x within the specified
> collating sequence, independent of the character encoding - and
> there's no reason not to make a wchar_t version.
static inline int coll(char c) {
return strchr("0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ", c);
}
...
switch (coll(c)) {
case coll('A')..coll('F'):
...
That requires two significant changes to C's switch syntax, but it
solves all of the objections I've seen in this thread so far, and it
wouldn't be difficult to implement at all.
With some implementation-specific hackery, you could also tap into the
Standard Library's collation tables so that it automatically adapted to
the user's locale, and it'd only require a tiny bit of work to handle
UTF-8 strings as well.
S
--
Stephen Sprunk "God does not play dice." --Albert Einstein
CCIE #3723 "God is an inveterate gambler, and He throws the
K5SSS dice at every possible opportunity." --Stephen Hawking
[toc] | [prev] | [next] | [standalone]
| From | Morris Dovey <mrdovey@iedu.com> |
|---|---|
| Date | 2015-05-25 00:51 -0500 |
| Message-ID | <mjud9c$6q4$1@speranza.aioe.org> |
| In reply to | #62569 |
On 5/24/15 7:26 PM, Stephen Sprunk wrote:
> static inline int coll(char c) {
> return strchr("0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ", c);
> }
> ...
> switch (coll(c)) {
> case coll('A')..coll('F'):
> ...
>
> That requires two significant changes to C's switch syntax, but it
> solves all of the objections I've seen in this thread so far, and it
> wouldn't be difficult to implement at all.
>
> With some implementation-specific hackery, you could also tap into the
> Standard Library's collation tables so that it automatically adapted to
> the user's locale, and it'd only require a tiny bit of work to handle
> UTF-8 strings as well.
I'd prefer to allow user-specified character sets and collation orders
for each switch statement. That would increase usefulness with not too
much additional compiler design complexity.
I did a bit of doodling to try to pin down what execution logic might
look like and produced this bit of pseudocode (note that 'case code' can
include a break statement):
char *seqstr; /* Pointer to collating sequence string */
int seqlen; /* Length of sequence string */
int switch; /* Switch target value */
int skip; /* Target matched, do not test again */
void collate(char *s) /* Register collating sequence */
{ seqstr = s;
seqlen = strlen(s);
}
int co(char x) /* Return index of x in sequence, or -1 */
{ for (int i=0; i<seqlen; i++) if (x == seqstr[i]) return i;
return -1;
}
int inrange(char min,char max) /* Case range test or skip */
{ int i1,i2;
if (skip) return 1;
i1 = co(min),
i2 = co(max);
skip = -1 != i1 && -1 != i2 && switch >= i1 && switch <= i2;
return skip;
}
collate("0123456789ΑΒΓΔΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΩ");
/* Switch (z) */ skip = 0; if (-1 != (switch = co(z))) do
{
/* case 'A'..'Z': */ if (!inrange('A','Z')) goto L1;
/* case code */
L1:
/* case 'H'..'Σ': */ if (!inrange('H','Σ')) goto L2;
/* case code */
L2:
/* default: */
/* case code */
}
else /* Invalid target */
What I have NOT accounted for is nested switch statements - nor did I
even try to deal with nested switch statements using different character
sets and/or collating orders. I think I know what kind of code structure
that might entail, but it's too late/early and I'm just not up to
dealing with that tonight. :-)
--
Morris Dovey
http://www.iedu.com/Solar
[toc] | [prev] | [next] | [standalone]
| From | Stephen Sprunk <stephen@sprunk.org> |
|---|---|
| Date | 2015-05-25 15:48 -0500 |
| Message-ID | <mk01p6$pd0$1@dont-email.me> |
| In reply to | #62580 |
On 25-May-15 00:51, Morris Dovey wrote:
> On 5/24/15 7:26 PM, Stephen Sprunk wrote:
>> static inline int coll(char c) {
>> return strchr("0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ", c);
>> }
>> ...
>> switch (coll(c)) {
>> case coll('A')..coll('F'):
>> ...
>>
>> That requires two significant changes to C's switch syntax, but it
>> solves all of the objections I've seen in this thread so far, and it
>> wouldn't be difficult to implement at all.
>>
>> With some implementation-specific hackery, you could also tap into the
>> Standard Library's collation tables so that it automatically adapted to
>> the user's locale, and it'd only require a tiny bit of work to handle
>> UTF-8 strings as well.
>
> I'd prefer to allow user-specified character sets and collation orders
> for each switch statement. That would increase usefulness with not too
> much additional compiler design complexity.
The two changes required to make the above example work are:
1. Allowing all compile-time constants for cases, not just "integer
constant expressions". C++ already has this.
2. Add support for numeric ranges. GCC already has this.
Note that my example does _not_ require any character-specific hackery
in the language itself. It'd be nice if the Standard Library provided a
function to access collation ordinals (in addition to strcoll() and
wcscoll(), which only compare two characters' ordinals), but that is
completely optional.
> I did a bit of doodling to try to pin down what execution logic might
> look like and produced this bit of pseudocode (note that 'case code' can
> include a break statement):
>
> char *seqstr; /* Pointer to collating sequence string */
> int seqlen; /* Length of sequence string */
> int switch; /* Switch target value */
> int skip; /* Target matched, do not test again */
>
> void collate(char *s) /* Register collating sequence */
> { seqstr = s;
> seqlen = strlen(s);
> }
>
> int co(char x) /* Return index of x in sequence, or -1 */
> { for (int i=0; i<seqlen; i++) if (x == seqstr[i]) return i;
> return -1;
> }
Why not just use strchr() as in my example? That also lets you get rid
of your seqlen variable. If you want to keep the latter, you could use
memchr() instead of an explicit loop.
You'd need to change that to strstr() for UTF-8 support, but that's a
minor change; it doesn't break the design.
> int inrange(char min,char max) /* Case range test or skip */
> { int i1,i2;
> if (skip) return 1;
> i1 = co(min),
> i2 = co(max);
> skip = -1 != i1 && -1 != i2 && switch >= i1 && switch <= i2;
> return skip;
> }
If you're going to do it that way, you might as well use strcoll() (or
wcscoll()) rather than rolling your own.
> What I have NOT accounted for is nested switch statements - nor did
> I even try to deal with nested switch statements using different
> character sets and/or collating orders. I think I know what kind of
> code structure that might entail, but it's too late/early and I'm
> just not up to dealing with that tonight. :-)
If that's truly necessary, then by leaning on the existing collation
functions, you could accommodate it by having each level change locale,
without any other changes to the language itself. That'd be slow, but I
suspect it's a rare enough use case to not matter.
S
--
Stephen Sprunk "God does not play dice." --Albert Einstein
CCIE #3723 "God is an inveterate gambler, and He throws the
K5SSS dice at every possible opportunity." --Stephen Hawking
[toc] | [prev] | [next] | [standalone]
| From | Morris Dovey <mrdovey@iedu.com> |
|---|---|
| Date | 2015-05-26 02:36 -0500 |
| Message-ID | <mk17qn$thv$1@speranza.aioe.org> |
| In reply to | #62618 |
On 5/25/15 3:48 PM, Stephen Sprunk wrote:
> On 25-May-15 00:51, Morris Dovey wrote:
>> On 5/24/15 7:26 PM, Stephen Sprunk wrote:
>>> static inline int coll(char c) {
>>> return strchr("0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ", c);
>>> }
>>> ...
>>> switch (coll(c)) {
>>> case coll('A')..coll('F'):
>>> ...
>>>
>>> That requires two significant changes to C's switch syntax, but it
>>> solves all of the objections I've seen in this thread so far, and it
>>> wouldn't be difficult to implement at all.
>>>
>>> With some implementation-specific hackery, you could also tap into the
>>> Standard Library's collation tables so that it automatically adapted to
>>> the user's locale, and it'd only require a tiny bit of work to handle
>>> UTF-8 strings as well.
>>
>> I'd prefer to allow user-specified character sets and collation orders
>> for each switch statement. That would increase usefulness with not too
>> much additional compiler design complexity.
>
> The two changes required to make the above example work are:
>
> 1. Allowing all compile-time constants for cases, not just "integer
> constant expressions". C++ already has this.
"All compile-time constants" could be pretty squirrely. How close do
floating point values need to be to a range bound to be classified as
'in' the range?
What non-C languages support is irrelevant. If C++ already has what you
need, then your problem is already solved and by insisting on a C
solution, you’re rejecting the very solution you’re proposing. :-P
> 2. Add support for numeric ranges. GCC already has this.
Goody for gcc – but it’s just one C compiler package out of a whole pile
of C compilers, and Gnu lacks imperial authority.
> Note that my example does _not_ require any character-specific hackery
> in the language itself. It'd be nice if the Standard Library provided a
> function to access collation ordinals (in addition to strcoll() and
> wcscoll(), which only compare two characters' ordinals), but that is
> completely optional.
You’re wanting to do pointer comparisons and I still prefer integer
comparisons. I’m probably not going to change my mind on this one
without seeing compelling reasons.
I think you’re missing an important point - that while the character set
for program code can be nailed down for a language language, programmers
can reasonably be expected to deal with textual data in a multitude of
languages - in Canada, for example, with both English and French
character sets and collating sequences - or in Greece with Greek, Latin,
Turkish, Arabic, and Macedonian textual data. For those reasons I would
argue that if we’re going to allow character ranges, the programmer
should be able to specify the character set and associated collating
sequence.
One of the reasons I picked Greek for my example, by the way, is that a
range of 'A'..'Z' only includes the first six letters of the Greek alphabet.
>
>> I did a bit of doodling to try to pin down what execution logic might
>> look like and produced this bit of pseudocode (note that 'case code' can
>> include a break statement):
>>
>> char *seqstr; /* Pointer to collating sequence string */
>> int seqlen; /* Length of sequence string */
>> int switch; /* Switch target value */
>> int skip; /* Target matched, do not test again */
>>
>> void collate(char *s) /* Register collating sequence */
>> { seqstr = s;
>> seqlen = strlen(s);
>> }
>>
>> int co(char x) /* Return index of x in sequence, or -1 */
>> { for (int i=0; i<seqlen; i++) if (x == seqstr[i]) return i;
>> return -1;
>> }
>
> Why not just use strchr() as in my example? That also lets you get rid
> of your seqlen variable. If you want to keep the latter, you could use
> memchr() instead of an explicit loop.
>
> You'd need to change that to strstr() for UTF-8 support, but that's a
> minor change; it doesn't break the design.
>
>> int inrange(char min,char max) /* Case range test or skip */
>> { int i1,i2;
>> if (skip) return 1;
>> i1 = co(min),
>> i2 = co(max);
>> skip = -1 != i1 && -1 != i2 && switch >= i1 && switch <= i2;
>> return skip;
>> }
>
> If you're going to do it that way, you might as well use strcoll() (or
> wcscoll()) rather than rolling your own.
Perhaps – but since I was writing pseudocode, I was more concerned with
clarity of concept than the library. Please feel free to tweak it any
way that pleases you.
The sharp programmer will probably notice that the character set
specified for a switch statement need only include those characters used
in the range specifications, and that by so limiting the character set
there are speed and memory advantages over hackish tricks with the
locale. :-D
>> What I have NOT accounted for is nested switch statements - nor did
>> I even try to deal with nested switch statements using different
>> character sets and/or collating orders. I think I know what kind of
>> code structure that might entail, but it's too late/early and I'm
>> just not up to dealing with that tonight. :-)
>
> If that's truly necessary, then by leaning on the existing collation
> functions, you could accommodate it by having each level change locale,
> without any other changes to the language itself. That'd be slow, but I
> suspect it's a rare enough use case to not matter.
It is truly necessary - the standard allows nested switch statements.
There was an unanswered request for possible syntax suggestions. I meant
to respond but got sidetracked. I can suggest
switch (x) using ("ABCDEF")
{ case 'A'..'F':
/* case code */
case 'G':
/* case code */
default:
/* case code */
}
--
Morris Dovey
http://www.iedu.com/Solar
[toc] | [prev] | [next] | [standalone]
| From | Morris Dovey <mrdovey@iedu.com> |
|---|---|
| Date | 2015-05-26 13:23 -0500 |
| Message-ID | <mk2dnj$4i0$1@speranza.aioe.org> |
| In reply to | #62628 |
On 5/26/15 2:36 AM, Morris Dovey wrote:
> There was an unanswered request for possible syntax suggestions. I meant
> to respond but got sidetracked. I can suggest
>
> switch (x) using ("ABCDEF")
> { case 'A'..'F':
> /* case code */
> case 'G':
> /* case code */
> default:
> /* case code */
> }
After sleeping on that, I like better:
switch (x)
{ case 'A'..'F' using ("ABCDEF"):
/* case code */
case 'G':
/* case code */
default:
/* case code */
}
--
Morris Dovey
http://www.iedu.com/Solar
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2015-05-27 00:55 +0100 |
| Message-ID | <87pp5mevxn.fsf@bsb.me.uk> |
| In reply to | #62655 |
Morris Dovey <mrdovey@iedu.com> writes:
> On 5/26/15 2:36 AM, Morris Dovey wrote:
>> There was an unanswered request for possible syntax suggestions. I meant
>> to respond but got sidetracked. I can suggest
>>
>> switch (x) using ("ABCDEF")
>> { case 'A'..'F':
>> /* case code */
>> case 'G':
>> /* case code */
>> default:
>> /* case code */
>> }
>
> After sleeping on that, I like better:
>
> switch (x)
> { case 'A'..'F' using ("ABCDEF"):
> /* case code */
> case 'G':
> /* case code */
> default:
> /* case code */
> }
I suppose you could even have:
switch (x)
{ case "ABCDEF":
/* case code */
case 'G':
/* case code */
default:
/* case code */
}
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | raltbos@xs4all.nl (Richard Bos) |
|---|---|
| Date | 2015-05-29 12:28 +0000 |
| Message-ID | <55685ac3.14685515@news.xs4all.nl> |
| In reply to | #62664 |
Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
> I suppose you could even have:
>
> switch (x)
> { case "ABCDEF":
> /* case code */
Well, except that there have already been calls to allow a switch to
compare on string literals, so that you could have
switch (permutation) {
case "ABC":
case "ACB":
/* code... */
case "CBA":
/* code... */
default:
/* code... */
}
So there'd need to be a way of disunconfusing those cases.
Once you start being creative with your desired additions to the
language, there is no end to the complications.
Richard
[toc] | [prev] | [next] | [standalone]
| From | Bartc <bc@freeuk.com> |
|---|---|
| Date | 2015-05-29 13:44 +0100 |
| Message-ID | <mk9mtn$uss$1@dont-email.me> |
| In reply to | #62784 |
On 29/05/2015 13:28, Richard Bos wrote:
> Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>
>> I suppose you could even have:
>>
>> switch (x)
>> { case "ABCDEF":
>> /* case code */
>
> Well, except that there have already been calls to allow a switch to
> compare on string literals, so that you could have
>
>
> switch (permutation) {
> case "ABC":
> case "ACB":
> /* code... */
> case "CBA":
> /* code... */
> default:
> /* code... */
> }
>
> So there'd need to be a way of disunconfusing those cases.
Presumably x would be a char or int type, so if matching with a string
literal, the intention can be assumed to be to match one of those
characters.
But 'permutation' would have to be a char* type, so this is string
matching. Doing "strcmp" however is not quite the same as the "==" kind
of matching that switch effectively does. It's not been well thought out.
> Once you start being creative with your desired additions to the
> language, there is no end to the complications.
Not really, if you know when to stop, and know what is suitable for the
language.
Your example is no problem at all for a scripting language, but it's
difficult to justify in C or to make it fit in.
(What /does/ suit C more is something like:
int permutation;
switch (permutation) {
case 'ABC':
case 'ACB':
etc.
Except that such char literals are probably badly defined, and with
Unicode becoming popular, that introduces problems.)
--
Bartc
[toc] | [prev] | [next] | [standalone]
| From | raltbos@xs4all.nl (Richard Bos) |
|---|---|
| Date | 2015-05-29 15:55 +0000 |
| Message-ID | <55688bde.27255812@news.xs4all.nl> |
| In reply to | #62787 |
Bartc <bc@freeuk.com> wrote: > On 29/05/2015 13:28, Richard Bos wrote: > > Once you start being creative with your desired additions to the > > language, there is no end to the complications. > > Not really, if you know when to stop, and know what is suitable for the > language. Yeah, and _if_ my aunt had as many bollocks as are talked in this thread, she'd be my uncle. Richard
[toc] | [prev] | [next] | [standalone]
Page 16 of 22 — ← Prev page 1 … 14 15 [16] 17 18 … 22 Next page →
Back to top | Article view | comp.lang.c
csiph-web