Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #146566 > unrolled thread
| Started by | DFS <nospam@dfs.com> |
|---|---|
| First post | 2019-10-04 13:00 -0400 |
| Last post | 2019-10-15 11:19 -0700 |
| Articles | 20 on this page of 483 — 31 participants |
Back to article view | Back to comp.lang.c
Sort char array DFS <nospam@dfs.com> - 2019-10-04 13:00 -0400
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-04 17:06 +0000
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-04 21:55 +0300
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-04 19:24 -0400
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-05 13:08 +0300
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-04 21:06 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-05 01:21 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-05 01:23 +0100
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-04 20:49 -0400
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-04 20:45 -0400
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-05 13:14 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-05 14:35 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-05 17:12 +0100
Re: Sort char array luser droog <luser.droog@gmail.com> - 2019-10-05 09:26 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-05 17:51 +0100
Re: Sort char array chad <cdalten@gmail.com> - 2019-10-15 09:00 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-15 19:29 +0300
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-05 18:13 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-05 21:09 +0100
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-05 13:22 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-05 21:45 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-06 00:17 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-06 16:32 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-06 15:54 +0100
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-06 08:07 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-06 17:39 +0100
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-06 12:52 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-06 21:26 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-07 01:37 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 01:10 +0100
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-06 17:32 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 02:02 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-07 09:41 +0200
Re: Sort char array mark.bluemel@gmail.com - 2019-10-07 00:39 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 10:59 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-07 13:19 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 12:42 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-07 13:57 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 15:01 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-07 17:42 +0300
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-07 17:20 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-07 19:33 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 18:22 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-08 02:27 +0300
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-07 17:02 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 08:53 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-08 12:28 +0100
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-08 11:47 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-09 02:02 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 00:50 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-10 03:03 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-10 01:51 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-10 10:31 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-10 11:57 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-10 14:24 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-10 14:41 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-10 16:17 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-10 18:09 +0100
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-10 17:38 +0000
Re: Sort char array already5chosen@yahoo.com - 2019-10-10 01:37 -0700
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-10 11:05 -0700
Re: Sort char array Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2019-10-10 14:33 -0400
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-10 12:20 -0700
Re: Sort char array Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2019-10-10 16:00 -0400
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-10 23:43 +0300
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-10 14:12 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-11 01:04 +0300
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-10 22:17 +0000
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-10 15:24 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-10 12:57 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-11 00:53 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-11 00:50 +0100
Re: Sort char array Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2019-10-12 03:42 +0800
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-11 22:16 +0100
Re: Sort char array raltbos@xs4all.nl (Richard Bos) - 2019-10-14 16:08 +0000
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 19:20 +0100
Re: Sort char array Ian Collins <ian-news@hotmail.com> - 2019-10-15 07:40 +1300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 20:24 +0100
Re: Sort char array Ian Collins <ian-news@hotmail.com> - 2019-10-15 08:33 +1300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 20:52 +0100
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-14 16:18 -0700
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-14 23:42 +0000
Re: Sort char array Ian Collins <ian-news@hotmail.com> - 2019-10-15 16:40 +1300
Re: Sort char array chad <cdalten@gmail.com> - 2019-10-15 05:10 -0700
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-14 12:00 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-09 12:33 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 14:22 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-09 15:35 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 16:15 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-09 20:24 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 20:42 +0100
Re: Sort char array already5chosen@yahoo.com - 2019-10-09 10:40 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-09 20:31 +0200
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-09 12:02 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-09 22:21 +0200
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-09 21:31 +0000
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-09 15:35 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-10 00:32 +0300
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-10 10:40 +0200
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-10 10:42 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-10 15:58 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-13 21:37 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-13 19:56 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-14 00:56 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 11:04 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-14 13:33 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-18 10:57 +0100
Re: Sort char array mark.bluemel@gmail.com - 2019-10-18 05:56 -0700
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-18 06:10 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-18 15:24 +0200
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-18 09:41 -0400
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-18 07:20 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-18 15:29 +0100
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-19 06:04 -0700
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-18 13:36 +0000
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-18 15:17 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-18 16:44 +0100
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-18 08:49 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-18 17:56 +0200
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-18 09:03 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-18 19:14 +0200
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-18 23:45 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-18 23:06 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-18 23:45 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-19 00:49 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-19 01:19 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-19 11:16 +0100
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-19 03:56 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-19 13:29 +0100
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-19 08:44 -0400
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-19 14:05 +0100
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-19 07:35 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-19 18:01 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-19 20:14 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-19 23:12 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-20 00:45 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-20 10:24 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 14:39 +0200
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-20 06:11 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 15:36 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-20 14:36 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 16:47 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-20 19:16 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 21:37 +0200
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-20 09:54 -0400
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-19 13:24 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-19 13:40 +0100
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-19 13:13 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-19 13:57 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 15:04 +0200
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-20 06:21 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 15:40 +0200
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-20 07:29 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 16:49 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-20 15:10 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 21:26 +0200
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-20 19:56 +0000
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 23:06 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-20 23:08 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-21 00:25 +0200
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-20 22:33 +0000
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-20 22:57 +0000
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-21 00:14 +0100
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-20 23:48 +0000
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-21 11:20 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-21 12:36 +0100
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-20 22:48 +0000
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-21 01:20 +0200
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-22 18:00 +0200
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-22 10:51 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-22 19:19 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-20 21:27 +0100
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-20 14:46 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-20 23:34 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-18 16:35 +0100
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-18 17:01 +0000
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-18 19:15 +0200
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-18 19:01 +0000
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 13:14 +0200
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-20 11:25 +0000
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-20 15:07 +0200
Re: Sort char array Melzzzzz <Melzzzzz@zzzzz.com> - 2019-10-18 16:58 +0000
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-14 08:06 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-14 19:55 +0300
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-15 03:24 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-15 12:39 +0300
Re: Sort char array already5chosen@yahoo.com - 2019-10-15 04:03 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-15 14:30 +0100
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-18 05:59 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-19 00:31 +0100
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-23 04:46 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-14 12:06 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-11 10:30 +0200
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-11 02:26 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-11 12:41 +0200
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-11 11:34 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-12 12:06 +0200
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-12 11:55 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-13 13:23 +0200
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-13 13:30 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-14 16:13 +0200
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-11 02:00 +0300
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-11 10:33 +0200
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-10 01:01 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-10 11:19 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-10 12:18 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-10 16:15 +0100
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-10 15:32 +0000
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-10 21:03 +0100
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-10 20:36 +0000
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-10 17:16 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-11 03:25 +0100
Re: Sort char array David Kleinecke <dkleinecke@gmail.com> - 2019-10-10 22:36 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-11 12:10 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-12 00:26 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-12 00:44 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-12 12:18 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-12 12:42 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-12 15:00 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-12 15:29 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-12 19:13 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-12 19:04 +0100
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-12 20:13 -0400
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-13 01:36 +0100
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-12 22:52 -0400
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-12 23:06 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-13 10:25 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-13 16:42 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-13 18:03 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-13 19:50 +0200
Re: Sort char array already5chosen@yahoo.com - 2019-10-14 12:27 -0700
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-15 10:26 +0200
Re: Sort char array Ike Naar <ike@sdf.lonestar.org> - 2019-10-14 21:02 +0000
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-14 01:39 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 01:51 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-14 12:16 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 10:45 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-14 13:16 +0300
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-14 03:34 -0700
Lack of language I/O support (was Re: Sort char array, many posts ago) mark.bluemel@gmail.com - 2019-10-14 03:54 -0700
Re: Lack of language I/O support (was Re: Sort char array, many posts ago) scott@slp53.sl.home (Scott Lurndal) - 2019-10-14 13:36 +0000
Re: Lack of language I/O support (was Re: Sort char array, many posts ago) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2019-10-14 09:49 -0400
Re: Lack of language I/O support (was Re: Sort char array, many posts ago) mark.bluemel@gmail.com - 2019-10-14 07:15 -0700
Re: Lack of language I/O support (was Re: Sort char array, many posts ago) scott@slp53.sl.home (Scott Lurndal) - 2019-10-14 14:55 +0000
Re: Lack of language I/O support (was Re: Sort char array, many posts ago) mark.bluemel@gmail.com - 2019-10-14 08:10 -0700
Re: Lack of language I/O support (was Re: Sort char array, many posts ago) scott@slp53.sl.home (Scott Lurndal) - 2019-10-14 16:21 +0000
Re: Lack of language I/O support (was Re: Sort char array, many posts ago) Siri Cruise <chine.bleu@yahoo.com> - 2019-10-14 09:25 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-14 14:57 +0300
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-14 08:24 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 16:40 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-14 16:17 +0200
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-14 23:45 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-15 00:03 +0100
Re: Sort char array Thiago Adams <thiago.adams@gmail.com> - 2019-10-14 05:30 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-14 16:05 +0300
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-14 07:55 -0700
Re: Sort char array Thiago Adams <thiago.adams@gmail.com> - 2019-10-14 10:58 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 14:36 +0100
Re: Sort char array Thiago Adams <thiago.adams@gmail.com> - 2019-10-14 11:03 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-14 19:28 +0100
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-14 08:17 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-15 00:26 +0300
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-15 11:55 +0300
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-16 04:24 -0700
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-16 07:19 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-16 18:17 +0300
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-17 05:43 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-17 18:01 +0300
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-19 00:39 +0300
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-19 06:00 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-11-08 18:38 +0300
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-11-08 22:03 -0800
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-12 18:49 -0400
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-13 00:25 +0100
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-12 23:44 -0400
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-12 13:45 +0100
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-13 19:05 -0400
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-12 13:16 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-13 00:12 +0100
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-13 14:18 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-13 23:10 +0100
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-14 23:52 -0400
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-15 11:48 -0400
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-15 18:14 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-15 20:31 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-15 20:11 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-15 20:34 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-15 22:05 +0200
Re: Sort char array already5chosen@yahoo.com - 2019-10-15 13:27 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-16 10:11 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-16 12:42 +0200
Re: Sort char array already5chosen@yahoo.com - 2019-10-16 04:02 -0700
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-17 05:51 -0700
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-18 10:18 -0400
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-18 12:05 -0700
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-23 05:42 -0700
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-23 05:02 -0700
Re: Sort char array raltbos@xs4all.nl (Richard Bos) - 2019-10-14 15:32 +0000
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-14 08:57 -0700
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-14 10:13 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-14 23:59 +0300
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-17 06:08 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-10 01:20 -0700
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-10 20:15 -0400
Re: Sort char array already5chosen@yahoo.com - 2019-10-11 04:00 -0700
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-11 07:53 -0400
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-11 11:20 -0400
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-11 11:16 -0700
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-11 14:43 -0400
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-11 11:51 -0700
Re: Sort char array raltbos@xs4all.nl (Richard Bos) - 2019-10-12 07:46 +0000
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-12 09:49 -0400
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-12 12:29 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-12 12:20 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-12 13:38 +0200
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-12 12:17 -0700
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-12 20:20 -0400
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-12 20:39 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-13 21:32 +0300
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-14 07:38 -0400
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-14 08:13 -0700
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-15 07:45 -0400
Re: Sort char array chad <cdalten@gmail.com> - 2019-10-15 05:12 -0700
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-15 13:04 -0700
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-17 10:14 -0700
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-15 12:24 -0400
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-16 04:12 -0700
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-16 14:21 -0700
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-16 19:12 -0400
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-16 16:33 -0700
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-16 19:48 -0400
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-18 06:57 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-13 21:22 +0300
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-11 01:02 +0300
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-07 17:01 +0200
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-07 12:24 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 12:18 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-07 14:11 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 15:22 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-07 17:17 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-07 20:52 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-08 00:45 +0300
Re: Sort char array already5chosen@yahoo.com - 2019-10-07 15:57 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-08 02:32 +0300
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 10:06 +0200
Re: Sort char array already5chosen@yahoo.com - 2019-10-08 03:21 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-09 00:34 +0300
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 11:23 +0200
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 09:59 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-08 11:39 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 14:05 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-08 15:06 +0100
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-08 14:38 +0000
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 17:34 +0200
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-08 16:38 +0000
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-08 07:55 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-08 18:31 +0300
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-08 16:39 +0000
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-08 19:57 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-08 18:09 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 22:16 +0200
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-08 23:58 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-08 22:19 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 17:39 +0200
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-09 00:12 +0300
Re: Sort char array already5chosen@yahoo.com - 2019-10-09 09:48 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 19:49 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 17:29 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-08 17:56 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-08 22:25 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 00:02 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-09 13:41 +0200
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 14:03 +0100
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-09 15:53 +0200
Re: Sort char array scott@slp53.sl.home (Scott Lurndal) - 2019-10-09 14:39 +0000
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 15:58 +0100
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-10 22:43 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-11 01:45 +0300
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-11 01:00 +0100
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-12 12:01 -0400
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-12 20:35 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-13 21:17 +0300
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-14 07:45 -0400
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-14 14:53 +0300
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-09 02:02 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-09 10:36 +0100
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-07 09:05 -0700
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-07 08:59 -0700
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-07 09:00 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-07 17:02 +0100
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-06 19:57 -0400
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-09 06:38 -0700
Re: Sort char array Bart <bc@freeuk.com> - 2019-10-05 17:14 +0100
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-05 13:06 -0400
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 02:24 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 05:13 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-06 16:04 +0300
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 07:13 -0700
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-06 18:23 -0400
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-06 15:41 +0300
Re: Sort char array Keith Thompson <kst-u@mib.org> - 2019-10-06 12:46 -0700
Re: Sort char array Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2019-10-07 04:00 +0800
Re: Sort char array David Brown <david.brown@hesbynett.no> - 2019-10-07 09:46 +0200
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-07 22:49 -0400
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-08 12:24 +0300
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-08 09:28 -0400
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-08 23:49 +0300
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-08 18:18 -0400
Re: Sort char array already5chosen@yahoo.com - 2019-10-08 03:34 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-08 14:36 +0300
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-08 15:34 +0300
Re: Sort char array already5chosen@yahoo.com - 2019-10-08 05:54 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-08 16:01 +0300
Re: Sort char array already5chosen@yahoo.com - 2019-10-08 06:31 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-09 00:30 +0300
Re: Sort char array already5chosen@yahoo.com - 2019-10-09 10:14 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-08 06:26 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-05 02:46 +0100
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-05 00:19 -0400
Re: Sort char array Barry Schwarz <schwarzb@dqel.com> - 2019-10-04 22:26 -0700
Re: OT Re: Sort char array Barry Schwarz <schwarzb@delq.com> - 2019-10-05 06:33 -0700
Re: Sort char array Bonita Montero <Bonita.Montero@gmail.com> - 2019-10-05 16:46 +0200
Re: Sort char array "Oliver S." <Follow.Me@gmx.net> - 2019-10-05 16:54 +0200
Re: Sort char array "Oliver S." <Follow.Me@gmx.net> - 2019-10-05 17:14 +0200
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-05 11:34 -0400
Re: Sort char array Mateusz Viste <mateusz@wont.tell> - 2019-10-05 15:43 +0000
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-05 17:29 -0400
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 02:14 -0700
Re: Sort char array Mateusz Viste <mateusz@wont.tell> - 2019-10-06 09:58 +0000
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 03:11 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 03:35 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-06 15:57 +0300
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-06 16:12 +0100
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-09 02:06 -0700
Re: Sort char array Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-10-07 07:28 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-07 17:51 +0100
Re: Sort char array Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2019-10-08 18:31 +0800
Re: Sort char array already5chosen@yahoo.com - 2019-10-08 03:59 -0700
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-09 02:14 -0700
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-08 14:34 +0300
Re: Sort char array Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2019-10-08 22:41 +0800
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 02:03 -0700
Re: Sort char array Bonita Montero <Bonita.Montero@gmail.com> - 2019-10-06 13:25 +0200
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-06 15:45 +0300
Re: Sort char array Bonita Montero <Bonita.Montero@gmail.com> - 2019-10-06 14:59 +0200
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-06 16:11 +0300
Re: Sort char array Bonita Montero <Bonita.Montero@gmail.com> - 2019-10-06 15:15 +0200
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-06 16:20 +0300
Re: Sort char array Bonita Montero <Bonita.Montero@gmail.com> - 2019-10-06 15:35 +0200
Re: Sort char array Richard Damon <Richard@Damon-Family.org> - 2019-10-06 13:04 -0400
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 08:44 -0700
Re: Sort char array Bonita Montero <Bonita.Montero@gmail.com> - 2019-10-06 18:01 +0200
Re: Sort char array already5chosen@yahoo.com - 2019-10-06 09:42 -0700
Re: Sort char array Bonita Montero <Bonita.Montero@gmail.com> - 2019-10-06 19:21 +0200
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-06 21:51 +0100
Re: Sort char array Bonita Montero <Bonita.Montero@gmail.com> - 2019-10-07 04:41 +0200
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-07 16:45 +0100
Re: Sort char array Anton Shepelev <anton.txt@g{oogle}mail.com> - 2019-10-07 19:11 +0300
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-07 21:10 +0100
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-08 00:43 +0300
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-07 15:51 -0400
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-09 01:48 -0700
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-07 00:42 -0400
Re: Sort char array John Bode <jfbode1029@gmail.com> - 2019-10-07 16:05 -0700
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-07 20:06 -0400
Re: Sort char array John Bode <jfbode1029@gmail.com> - 2019-10-08 08:34 -0700
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-08 01:09 +0100
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-07 20:12 -0400
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-08 01:44 +0100
Re: Sort char array DFS <nospam@dfs.com> - 2019-10-07 22:02 -0400
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-08 03:24 +0100
Re: Sort char array Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-10-09 01:42 +0100
Re: Sort char array John Bode <jfbode1029@gmail.com> - 2019-10-09 11:14 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-10 00:52 +0300
Re: Sort char array John Bode <jfbode1029@gmail.com> - 2019-10-08 08:20 -0700
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-09 00:20 +0300
Re: Sort char array James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-10-08 18:48 -0400
Re: Sort char array Anton Shepelev <anton.txt@gmail.com> - 2019-10-09 02:07 +0300
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-09 02:29 -0700
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-09 09:43 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-09 09:37 -0700
Re: Sort char array Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-10-09 02:22 -0700
Re: Sort char array already5chosen@yahoo.com - 2019-10-15 11:19 -0700
Page 13 of 25 — ← Prev page 1 … 11 12 [13] 14 15 … 25 Next page →
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2019-10-14 13:36 +0000 |
| Subject | Re: Lack of language I/O support (was Re: Sort char array, many posts ago) |
| Message-ID | <9R_oF.51672$SW2.38929@fx24.iad> |
| In reply to | #146935 |
mark.bluemel@gmail.com writes: >On Monday, 14 October 2019 11:34:58 UTC+1, Malcolm McLean wrote: > >> C decided that there would be no input output statements, only functions, >> which were implemented either in non-portable C or in assembly. >> However that was an unusual design decision at the time. > >I'm not convinced it was that unusual. I worked for Prime Computer in the >early '80s and the operating system and utilties (dating back to the early >'70s) were written in a mixture of Assembler, Fortran (yes, really) and >2 PL/1 derivatives (PL/P and SPL), and as far as I remember all I/O was >done via function calls - certainly neither PL/1 variant had any language >I/O support. Which was rare in the day; compare with Fortran, COBOL, Pascal, etc.
[toc] | [prev] | [next] | [standalone]
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Date | 2019-10-14 09:49 -0400 |
| Subject | Re: Lack of language I/O support (was Re: Sort char array, many posts ago) |
| Message-ID | <qo1ucd$a9q$4@dont-email.me> |
| In reply to | #146942 |
Scott Lurndal wrote: > mark.bluemel@gmail.com writes: >>On Monday, 14 October 2019 11:34:58 UTC+1, Malcolm McLean wrote: >> >>> C decided that there would be no input output statements, only >>> functions, which were implemented either in non-portable C or in >>> assembly. However that was an unusual design decision at the time. >> >>I'm not convinced it was that unusual. I worked for Prime Computer in the >>early '80s and the operating system and utilties (dating back to the early >>'70s) were written in a mixture of Assembler, Fortran (yes, really) and >>2 PL/1 derivatives (PL/P and SPL), and as far as I remember all I/O was >>done via function calls - certainly neither PL/1 variant had any language >>I/O support. > > Which was rare in the day; compare with Fortran, COBOL, Pascal, etc. PL/I had the "GET" and "PUT" keywords, so Mark's experience may have been site-related. Most (afaict, all) contemporary high-level languages had I/O facilities built into the language structure as well: add to the list RPG and APL. -- Lew Pitcher "In Skills, We Trust"
[toc] | [prev] | [next] | [standalone]
| From | mark.bluemel@gmail.com |
|---|---|
| Date | 2019-10-14 07:15 -0700 |
| Subject | Re: Lack of language I/O support (was Re: Sort char array, many posts ago) |
| Message-ID | <2a8c26a6-0746-45ff-9254-52d19a3378df@googlegroups.com> |
| In reply to | #146944 |
On Monday, 14 October 2019 14:49:11 UTC+1, Lew Pitcher wrote: > Scott Lurndal wrote: > > > mark.bluemel@gmail.com writes: > >>On Monday, 14 October 2019 11:34:58 UTC+1, Malcolm McLean wrote: > >> > >>> C decided that there would be no input output statements, only > >>> functions, which were implemented either in non-portable C or in > >>> assembly. However that was an unusual design decision at the time. > >> > >>I'm not convinced it was that unusual. I worked for Prime Computer in the > >>early '80s and the operating system and utilties (dating back to the early > >>'70s) were written in a mixture of Assembler, Fortran (yes, really) and > >>2 PL/1 derivatives (PL/P and SPL), and as far as I remember all I/O was > >>done via function calls - certainly neither PL/1 variant had any language > >>I/O support. > > > > Which was rare in the day; compare with Fortran, COBOL, Pascal, etc. > > PL/I had the "GET" and "PUT" keywords, so Mark's experience may have been > site-related. Most (afaict, all) contemporary high-level languages had I/O > facilities built into the language structure as well: add to the list RPG > and APL. SPL and PL/P were the Prime internal systems programming languages, which explicitly had no native language I/O. Both were PL/1 derived, with SPL closely resembling PL/1G but (to repeat and emphasise) without I/O support as part of the language. PL/P was similar, but more limited. My point is that in the same sort of timeframe as Unix and C, another operating system was being implemented using compiled languages, rather than assembler, and with I/O being implemented purely by function calls.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2019-10-14 14:55 +0000 |
| Subject | Re: Lack of language I/O support (was Re: Sort char array, many posts ago) |
| Message-ID | <T%%oF.21115$HU2.18409@fx26.iad> |
| In reply to | #146946 |
mark.bluemel@gmail.com writes: >On Monday, 14 October 2019 14:49:11 UTC+1, Lew Pitcher wrote: >> Scott Lurndal wrote: >> >> > mark.bluemel@gmail.com writes: >> >>On Monday, 14 October 2019 11:34:58 UTC+1, Malcolm McLean wrote: >> >> >> >>> C decided that there would be no input output statements, only >> >>> functions, which were implemented either in non-portable C or in >> >>> assembly. However that was an unusual design decision at the time. >> >> >> >>I'm not convinced it was that unusual. I worked for Prime Computer in the >> >>early '80s and the operating system and utilties (dating back to the early >> >>'70s) were written in a mixture of Assembler, Fortran (yes, really) and >> >>2 PL/1 derivatives (PL/P and SPL), and as far as I remember all I/O was >> >>done via function calls - certainly neither PL/1 variant had any language >> >>I/O support. >> > >> > Which was rare in the day; compare with Fortran, COBOL, Pascal, etc. >> >> PL/I had the "GET" and "PUT" keywords, so Mark's experience may have been >> site-related. Most (afaict, all) contemporary high-level languages had I/O >> facilities built into the language structure as well: add to the list RPG >> and APL. > >SPL and PL/P were the Prime internal systems programming languages, which >explicitly had no native language I/O. Both were PL/1 derived, with SPL >closely resembling PL/1G but (to repeat and emphasise) without I/O support >as part of the language. PL/P was similar, but more limited. > >My point is that in the same sort of timeframe as Unix and C, another >operating system was being implemented using compiled languages, rather >than assembler, and with I/O being implemented purely by function calls. The Burroughs Large systems mainframe operating system had been written in high level languages (Algol derivitives) from the mid 1960s, FWIW. The Medium systems mainframe MCP was written in a high-level modula-like language called SPRITE from the early 1980's.
[toc] | [prev] | [next] | [standalone]
| From | mark.bluemel@gmail.com |
|---|---|
| Date | 2019-10-14 08:10 -0700 |
| Subject | Re: Lack of language I/O support (was Re: Sort char array, many posts ago) |
| Message-ID | <a60449cc-33b6-44d2-9ac6-895464a18ca0@googlegroups.com> |
| In reply to | #146949 |
On Monday, 14 October 2019 15:55:54 UTC+1, Scott Lurndal wrote: > mark.bluemel@gmail.com writes: > >On Monday, 14 October 2019 14:49:11 UTC+1, Lew Pitcher wrote: > >> Scott Lurndal wrote: > >> > >> > mark.bluemel@gmail.com writes: > >> >>On Monday, 14 October 2019 11:34:58 UTC+1, Malcolm McLean wrote: > >> >> > >> >>> C decided that there would be no input output statements, only > >> >>> functions, which were implemented either in non-portable C or in > >> >>> assembly. However that was an unusual design decision at the time. > >> >> > >> >>I'm not convinced it was that unusual. I worked for Prime Computer in the > >> >>early '80s and the operating system and utilties (dating back to the early > >> >>'70s) were written in a mixture of Assembler, Fortran (yes, really) and > >> >>2 PL/1 derivatives (PL/P and SPL), and as far as I remember all I/O was > >> >>done via function calls - certainly neither PL/1 variant had any language > >> >>I/O support. > >> > > >> > Which was rare in the day; compare with Fortran, COBOL, Pascal, etc. > >> > >> PL/I had the "GET" and "PUT" keywords, so Mark's experience may have been > >> site-related. Most (afaict, all) contemporary high-level languages had I/O > >> facilities built into the language structure as well: add to the list RPG > >> and APL. > > > >SPL and PL/P were the Prime internal systems programming languages, which > >explicitly had no native language I/O. Both were PL/1 derived, with SPL > >closely resembling PL/1G but (to repeat and emphasise) without I/O support > >as part of the language. PL/P was similar, but more limited. > > > >My point is that in the same sort of timeframe as Unix and C, another > >operating system was being implemented using compiled languages, rather > >than assembler, and with I/O being implemented purely by function calls. > > The Burroughs Large systems mainframe operating system had been written in high level > languages (Algol derivitives) from the mid 1960s, FWIW. The Medium systems > mainframe MCP was written in a high-level modula-like language called SPRITE > from the early 1980's. Thanks for that, Scott. Interesting.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2019-10-14 16:21 +0000 |
| Subject | Re: Lack of language I/O support (was Re: Sort char array, many posts ago) |
| Message-ID | <sg1pF.6996$xZ1.563@fx30.iad> |
| In reply to | #146951 |
mark.bluemel@gmail.com writes: >On Monday, 14 October 2019 15:55:54 UTC+1, Scott Lurndal wrote: >> mark.bluemel@gmail.com writes: >> >On Monday, 14 October 2019 14:49:11 UTC+1, Lew Pitcher wrote: >> >> Scott Lurndal wrote: >> >> >> >> > mark.bluemel@gmail.com writes: >> >> >>On Monday, 14 October 2019 11:34:58 UTC+1, Malcolm McLean wrote: >> >> >> >> >> >>> C decided that there would be no input output statements, only >> >> >>> functions, which were implemented either in non-portable C or in >> >> >>> assembly. However that was an unusual design decision at the time. >> >> >> >> >> >>I'm not convinced it was that unusual. I worked for Prime Computer in the >> >> >>early '80s and the operating system and utilties (dating back to the early >> >> >>'70s) were written in a mixture of Assembler, Fortran (yes, really) and >> >> >>2 PL/1 derivatives (PL/P and SPL), and as far as I remember all I/O was >> >> >>done via function calls - certainly neither PL/1 variant had any language >> >> >>I/O support. >> >> > >> >> > Which was rare in the day; compare with Fortran, COBOL, Pascal, etc. >> >> >> >> PL/I had the "GET" and "PUT" keywords, so Mark's experience may have been >> >> site-related. Most (afaict, all) contemporary high-level languages had I/O >> >> facilities built into the language structure as well: add to the list RPG >> >> and APL. >> > >> >SPL and PL/P were the Prime internal systems programming languages, which >> >explicitly had no native language I/O. Both were PL/1 derived, with SPL >> >closely resembling PL/1G but (to repeat and emphasise) without I/O support >> >as part of the language. PL/P was similar, but more limited. >> > >> >My point is that in the same sort of timeframe as Unix and C, another >> >operating system was being implemented using compiled languages, rather >> >than assembler, and with I/O being implemented purely by function calls. >> >> The Burroughs Large systems mainframe operating system had been written in high level >> languages (Algol derivitives) from the mid 1960s, FWIW. The Medium systems >> mainframe MCP was written in a high-level modula-like language called SPRITE >> from the early 1980's. > >Thanks for that, Scott. Interesting. Sure. And we must not leave out the HP-3000 Multiprogramming Executive (MPE) which was written in the high-level language SPL, which allowed direct access to the stack (and inline assembly). The Burroughs medium systems COBOL68 compiler also allowed inline assembly (ENTER SYMBOLIC).
[toc] | [prev] | [next] | [standalone]
| From | Siri Cruise <chine.bleu@yahoo.com> |
|---|---|
| Date | 2019-10-14 09:25 -0700 |
| Subject | Re: Lack of language I/O support (was Re: Sort char array, many posts ago) |
| Message-ID | <chine.bleu-654D87.09255014102019@reader.eternal-september.org> |
| In reply to | #146951 |
In article <a60449cc-33b6-44d2-9ac6-895464a18ca0@googlegroups.com>,
mark.bluemel@gmail.com wrote:
> > The Burroughs Large systems mainframe operating system had been written in
> > high level
> > languages (Algol derivitives) from the mid 1960s, FWIW. The Medium
> > systems
> > mainframe MCP was written in a high-level modula-like language called
> > SPRITE
> > from the early 1980's.
>
> Thanks for that, Scott. Interesting.
Algol 60/61 had no I/O, not even functions. Algol 68 had standardised I/O
functions which used a bit of magic for the argument list.
Two of the first proposed Algol I/O functions where insymbol and outsymbol:
integer character offset := insymbol(file, string);
The next symbol in file is read. The symbol is located in
the string and its offet returned.
outsymbol(file, string, i)
Output the ith symbol of string.
--
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted. @
'I desire mercy, not sacrifice.' /|\
The first law of discordiamism: The more energy This post / \
to make order is nore energy made into entropy. insults Islam. Mohammed
[toc] | [prev] | [next] | [standalone]
| From | Anton Shepelev <anton.txt@g{oogle}mail.com> |
|---|---|
| Date | 2019-10-14 14:57 +0300 |
| Message-ID | <20191014145756.4f3380a33eb71c4ff3d784a7@g{oogle}mail.com> |
| In reply to | #146934 |
Malcolm McLean to Anton Shepelev: >>True, but in my opinion the functions of a programming >>language are best implemented in this language. > >C decided that there would be no input output statements, >only functions,-> A good decision that allows for better decoupling. >-> which were implemented either in non-portable C or in >assembly. However that was an unusual design decision at >the time. > >The formatting of output isn't output itself, of course, >but it is closely tied to it. I think that formatting belongs to generic string manipulations, well implementable in a portable manner. -- () ascii ribbon campaign - against html e-mail /\ http://preview.tinyurl.com/qcy6mjc [archived]
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2019-10-14 08:24 -0700 |
| Message-ID | <86eezf73ky.fsf@linuxsc.com> |
| In reply to | #146930 |
Bart <bc@freeuk.com> writes: > [on implementing type-safe variadic arguments, for things like printf] > > No doubt Tim Rentsch would be able to wangle some solution, but [...] One difference between Bart and myself is that I am driven to solve problems whereas Bart is driven to create them.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2019-10-14 16:40 +0100 |
| Message-ID | <8G0pF.3194187$c8w1.2042004@fx08.am4> |
| In reply to | #146954 |
On 14/10/2019 16:24, Tim Rentsch wrote: > Bart <bc@freeuk.com> writes: > >> [on implementing type-safe variadic arguments, for things like printf] >> >> No doubt Tim Rentsch would be able to wangle some solution, but [...] > > One difference between Bart and myself is that I am driven > to solve problems whereas Bart is driven to create them. > I prefer aesthetically pleasing solutions. Especially if they impact on user-code. And, of course, easy ones.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2019-10-14 16:17 +0200 |
| Message-ID | <qo201q$mmp$1@dont-email.me> |
| In reply to | #146929 |
On 14/10/2019 11:16, Anton Shepelev wrote: > Bart: > >> If compilers can warn about incorrect formats, then why >> can't just insert the correct ones? > > Because that would be, as in your example, implementing a > funciton in the compiler rather than in the language being > compiled. > It would also cause trouble for things like international code where the printf (or printf-like functions) format strings get looked up in a list of translations. I think the warning is a lot safer than having the compiler try to change the code on the fly.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2019-10-14 23:45 +0100 |
| Message-ID | <87imor3q0i.fsf@bsb.me.uk> |
| In reply to | #146947 |
David Brown <david.brown@hesbynett.no> writes:
> On 14/10/2019 11:16, Anton Shepelev wrote:
>> Bart:
>>
>>> If compilers can warn about incorrect formats, then why
>>> can't just insert the correct ones?
>>
>> Because that would be, as in your example, implementing a
>> funciton in the compiler rather than in the language being
>> compiled.
>>
> It would also cause trouble for things like international code where the
> printf (or printf-like functions) format strings get looked up in a list
> of translations.
>
> I think the warning is a lot safer than having the compiler try to
> change the code on the fly.
Changing the string seems like a hack to me. I'd alter printf to allow
a type indicator to be passed so that
printf("%d %? %c\n", a, b, c);
becomes the call
printf("%d %? %c\n", a, _PTYPE_INT, b, c);
with the type indicator being added by the compiler. For a quick
version, the type indicator could be the conversion specifier ('d' in
this case).
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2019-10-15 00:03 +0100 |
| Message-ID | <s97pF.850641$RU2.257719@fx21.am4> |
| In reply to | #146977 |
On 14/10/2019 23:45, Ben Bacarisse wrote:
> David Brown <david.brown@hesbynett.no> writes:
>
>> On 14/10/2019 11:16, Anton Shepelev wrote:
>>> Bart:
>>>
>>>> If compilers can warn about incorrect formats, then why
>>>> can't just insert the correct ones?
>>>
>>> Because that would be, as in your example, implementing a
>>> funciton in the compiler rather than in the language being
>>> compiled.
>>>
>> It would also cause trouble for things like international code where the
>> printf (or printf-like functions) format strings get looked up in a list
>> of translations.
>>
>> I think the warning is a lot safer than having the compiler try to
>> change the code on the fly.
>
> Changing the string seems like a hack to me. I'd alter printf to allow
> a type indicator to be passed so that
>
> printf("%d %? %c\n", a, b, c);
>
> becomes the call
>
> printf("%d %? %c\n", a, _PTYPE_INT, b, c);
>
> with the type indicator being added by the compiler. For a quick
> version, the type indicator could be the conversion specifier ('d' in
> this case).
The string isn't changed; it's replaced, as the first argument, by a new
one. So it's not much different from your proposal, which inserts a new
argument.
Some issues with it:
* The format string still needs to be visible
* The __PTYPE_INT indicator enumerations have to be known to both the
compiler, and the library that implements printf
* If using "%d" in place of _PTYPE_INT, then it makes it little
different from my proposal, but requires pushing and retrieving more
arguments
* If used with a printf that does not recognise %?, then the __PTYPE_INT
in the argument will be output by the next conventional format code. If
this is %s, then it will go badly wrong. (With %d, it will just print
%d.) This applies also to any functions that try to interpret format codes.
To summarise, my proposal involved replacing the first format string
with a new one by the compiler, but could work with existing printf
implementations with no changes.
It would only go badly wrong, other than printing the wrong stuff, if a
char* value was passed that didn't point to a zero-terminated string.
But that would happen with %s too.
[toc] | [prev] | [next] | [standalone]
| From | Thiago Adams <thiago.adams@gmail.com> |
|---|---|
| Date | 2019-10-14 05:30 -0700 |
| Message-ID | <5d77c8a4-2179-4c6c-93ec-40eb9993924b@googlegroups.com> |
| In reply to | #146928 |
On Sunday, October 13, 2019 at 9:51:37 PM UTC-3, Bart wrote:
...
> I've just done a 30-minute experiment on my compiler to see how
> practical it was, using a new "%?" format which adapts to the actual
> type. With this program:
>
> #include <stdio.h>
>
> int a = 100;
> double b = 92.54;
> char *c = "hello";
>
> int main(void) {
> printf("A=%? B=%? C=%?", a, b, c);
> }
>
This is something I also could do I my C preprocessor. The way
languages are doing nowadays is simpler than that.
#include <stdio.h>
int a = 100;
double b = 92.54;
char *c = "hello";
int main(void) {
printf($"A={a} B={b} C={c}");
}
and the preprocessor will expand $"A={a}? B={b}? C={c}?"
in to parts.
printf("A=%d B=%f C=%s" , a, b, c);
References for other languages:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals
https://docs.microsoft.com/pt-br/dotnet/csharp/language-reference/tokens/interpolated
[toc] | [prev] | [next] | [standalone]
| From | Anton Shepelev <anton.txt@g{oogle}mail.com> |
|---|---|
| Date | 2019-10-14 16:05 +0300 |
| Message-ID | <20191014160503.233cf403a06f16d35f284e9a@g{oogle}mail.com> |
| In reply to | #146940 |
Thiago Adams:
>The way
>languages are doing nowadays is simpler than that.
>
>
> #include <stdio.h>
>
> int a = 100;
> double b = 92.54;
> char *c = "hello";
>
> int main(void) {
> printf($"A={a} B={b} C={c}");
> }
String interpolation is again an extra-linguistic mechanism
not expressible in terms of operations on typed variables.
Futhermore, it has a limited utility because the format
string cannot be reused, but I think people would appreciate
a type-aware printf even in the form of a preprocessor mechanism.
--
() ascii ribbon campaign - against html e-mail
/\ http://preview.tinyurl.com/qcy6mjc [archived]
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2019-10-14 07:55 -0700 |
| Message-ID | <86v9sr74xd.fsf@linuxsc.com> |
| In reply to | #146941 |
Anton Shepelev <anton.txt@g{oogle}mail.com> writes:
> [...] I think people would appreciate a type-aware printf even
> in the form of a preprocessor mechanism.
Why don't you try writing one, in standard C11 using the
existing C preprocessor? See how far you can get.
[toc] | [prev] | [next] | [standalone]
| From | Thiago Adams <thiago.adams@gmail.com> |
|---|---|
| Date | 2019-10-14 10:58 -0700 |
| Message-ID | <c51d89ac-b8d4-4f60-adca-54e8dbb67922@googlegroups.com> |
| In reply to | #146941 |
On Monday, October 14, 2019 at 10:05:13 AM UTC-3, Anton Shepelev wrote:
> Thiago Adams:
>
> >The way
> >languages are doing nowadays is simpler than that.
> >
> >
> > #include <stdio.h>
> >
> > int a = 100;
> > double b = 92.54;
> > char *c = "hello";
> >
> > int main(void) {
> > printf($"A={a} B={b} C={c}");
> > }
>
> String interpolation is again an extra-linguistic mechanism
> not expressible in terms of operations on typed variables.
> Futhermore, it has a limited utility because the format
> string cannot be reused, but I think people would appreciate
> a type-aware printf even in the form of a preprocessor mechanism.
I think the mechanism can be optional and even mixed, giving
an option to add extra information.
(String interpolation in javascript creates a new string dynamically,
and for this C feature I would create two arguments statically
to be used in printf -like functions.
)
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2019-10-14 14:36 +0100 |
| Message-ID | <xR_oF.785868$3x5.370003@fx14.am4> |
| In reply to | #146940 |
On 14/10/2019 13:30, Thiago Adams wrote:
> On Sunday, October 13, 2019 at 9:51:37 PM UTC-3, Bart wrote:
> ...
>> I've just done a 30-minute experiment on my compiler to see how
>> practical it was, using a new "%?" format which adapts to the actual
>> type. With this program:
>>
>> #include <stdio.h>
>>
>> int a = 100;
>> double b = 92.54;
>> char *c = "hello";
>>
>> int main(void) {
>> printf("A=%? B=%? C=%?", a, b, c);
>> }
>>
>
> This is something I also could do I my C preprocessor.
This is your special preprocessor, rather that C's one?
Because I don't think then CPP is capable of providing an acceptable
solution.
> The way
> languages are doing nowadays is simpler than that.
> int main(void) {
> printf($"A={a} B={b} C={c}");
> }
>
> and the preprocessor will expand $"A={a}? B={b}? C={c}?"
> in to parts.
>
> printf("A=%d B=%f C=%s" , a, b, c);
In my language this doesn't even need a format string:
print =a, =b, =c
I'm not sure how much simpler it can get.
The '=' inserts a constant string (eg. "A=", "B=") in front of each
expression.
(This can be added to my C experiment, eg. as "%=?", but requires
expression stringify, which is a tricky add-on if it doesn't already
exist. But if I do it (a 5-minute job for this test), then the printf
call in my example becomes:
printf("%=? %=? %=?", a, b, c);
The format string now becomes reusable, but more importantly does not
need maintaining if the expressions being printed change. However the
expression-to-string conversion needs to be done properly, and in C
terms. Because if I do this now:
printf("%=?", a+b);
The output is:
(DOUBLE(A)+B)=192.540000
in my language's syntax, and including any implicit conversions. But it
will suffice for debugging which is what "=" is used for mainly.)
[toc] | [prev] | [next] | [standalone]
| From | Thiago Adams <thiago.adams@gmail.com> |
|---|---|
| Date | 2019-10-14 11:03 -0700 |
| Message-ID | <e1845c86-b020-4440-a83f-8e25323c22c2@googlegroups.com> |
| In reply to | #146943 |
On Monday, October 14, 2019 at 10:36:37 AM UTC-3, Bart wrote:
> On 14/10/2019 13:30, Thiago Adams wrote:
> > On Sunday, October 13, 2019 at 9:51:37 PM UTC-3, Bart wrote:
> > ...
> >> I've just done a 30-minute experiment on my compiler to see how
> >> practical it was, using a new "%?" format which adapts to the actual
> >> type. With this program:
> >>
> >> #include <stdio.h>
> >>
> >> int a = 100;
> >> double b = 92.54;
> >> char *c = "hello";
> >>
> >> int main(void) {
> >> printf("A=%? B=%? C=%?", a, b, c);
> >> }
> >>
> >
> > This is something I also could do I my C preprocessor.
>
> This is your special preprocessor, rather that C's one?
Yes. But I haven't implemented it yet. I just had considered
this implementation.
(
and C++ RAW strings
https://en.cppreference.com/w/cpp/language/string_literal
)
> Because I don't think then CPP is capable of providing an acceptable
> solution.
Yes.
>
> > The way
> > languages are doing nowadays is simpler than that.
>
> > int main(void) {
> > printf($"A={a} B={b} C={c}");
> > }
> >
> > and the preprocessor will expand $"A={a}? B={b}? C={c}?"
> > in to parts.
> >
> > printf("A=%d B=%f C=%s" , a, b, c);
>
> In my language this doesn't even need a format string:
>
> print =a, =b, =c
>
> I'm not sure how much simpler it can get.
>
> The '=' inserts a constant string (eg. "A=", "B=") in front of each
> expression.
>
> (This can be added to my C experiment, eg. as "%=?", but requires
> expression stringify, which is a tricky add-on if it doesn't already
> exist. But if I do it (a 5-minute job for this test), then the printf
> call in my example becomes:
>
> printf("%=? %=? %=?", a, b, c);
>
> The format string now becomes reusable, but more importantly does not
> need maintaining if the expressions being printed change. However the
> expression-to-string conversion needs to be done properly, and in C
> terms. Because if I do this now:
>
> printf("%=?", a+b);
>
> The output is:
>
> (DOUBLE(A)+B)=192.540000
>
> in my language's syntax, and including any implicit conversions. But it
> will suffice for debugging which is what "=" is used for mainly.)
The other feature missing feature in printf is a custom callback
printf("%callback", MyPrint, pMyStruct);
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2019-10-14 19:28 +0100 |
| Message-ID | <j73pF.908451$ir6.454978@fx16.am4> |
| In reply to | #146964 |
On 14/10/2019 19:03, Thiago Adams wrote:
> The other feature missing feature in printf is a custom callback
>
> printf("%callback", MyPrint, pMyStruct);
Well, %c can't be used here, as that is a valid format spec.
But I think a C implementation of such a thing has been done by Tim
Rentsch. Look for articles about 'printx'.
At a somewhat higher level, a language would be looking for a 'tostring'
operation on each argument to its print function. This would be
overloaded for basic types of the language (what we've been trying to do
with printf), and for user callbacks, that could also be another
language-supplied mechanism.
It doesn't need to be full OOP, just a way to associated a user-function
taking with a specification combination of 'tostring' with a type.
[toc] | [prev] | [next] | [standalone]
Page 13 of 25 — ← Prev page 1 … 11 12 [13] 14 15 … 25 Next page →
Back to top | Article view | comp.lang.c
csiph-web