Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #124080 > unrolled thread
| Started by | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| First post | 2017-12-09 16:20 -0800 |
| Last post | 2017-12-24 21:04 -0800 |
| Articles | 20 on this page of 320 — 28 participants |
Back to article view | Back to comp.lang.c
Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-09 16:20 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-10 00:31 +0000
Re: Auto-execute code at exit? gordonb.k2333@burditt.org (Gordon Burditt) - 2017-12-09 20:40 -0600
Re: Auto-execute code at exit? fir <profesor.fir@gmail.com> - 2017-12-10 02:21 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-10 11:50 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-10 04:19 -0800
Re: Auto-execute code at exit? fir <profesor.fir@gmail.com> - 2017-12-10 04:32 -0800
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-10 04:43 -0800
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-10 05:03 -0800
Who's a troll now? (Was: Auto-execute code at exit?) gazelle@shell.xmission.com (Kenny McCormack) - 2017-12-10 14:01 +0000
Re: Auto-execute code at exit? scott@slp53.sl.home (Scott Lurndal) - 2017-12-11 15:19 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 15:46 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 08:04 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 18:35 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 11:09 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 20:28 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 12:38 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 09:07 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-12 11:45 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 13:50 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-12 19:29 +0000
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-13 08:52 +1300
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 23:04 +0100
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 21:08 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-12 21:40 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 23:22 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-12 15:54 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 00:11 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-12 17:38 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 10:44 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-13 03:12 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-13 10:16 +0100
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-12 09:35 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 20:42 +0100
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 09:02 +0100
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-12 21:34 +1300
Re: Auto-execute code at exit? scott@slp53.sl.home (Scott Lurndal) - 2017-12-11 18:37 +0000
Re: Auto-execute code at exit? Manfred <noname@invalid.add> - 2017-12-11 19:39 +0100
Re: Auto-execute code at exit? Gordon Burditt <gordon@hammy.burditt.org> - 2017-12-12 20:54 -0600
Re: Auto-execute code at exit? Richard Damon <Richard@Damon-Family.org> - 2017-12-09 19:32 -0500
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-10 13:36 +1300
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-09 17:14 -0800
Re: Auto-execute code at exit? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-12-09 21:49 -0700
Re: Auto-execute code at exit? "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-12-10 11:04 +0100
Re: Auto-execute code at exit? "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2017-12-10 20:22 +0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-10 18:10 +0100
Re: Auto-execute code at exit? Melzzzzz <Melzzzzz@zzzzz.com> - 2017-12-10 20:48 +0000
Auto-execute code at exit? mark.bluemel@gmail.com - 2017-12-10 10:59 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-10 20:37 +0100
Re: Auto-execute code at exit? James Kuyper <jameskuyper@verizon.net> - 2017-12-10 15:58 -0500
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-10 22:59 +0000
Re: Auto-execute code at exit? Melzzzzz <Melzzzzz@zzzzz.com> - 2017-12-11 02:34 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 15:33 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-11 16:42 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 15:52 +0000
Re: Auto-execute code at exit? gazelle@shell.xmission.com (Kenny McCormack) - 2017-12-11 15:53 +0000
Re: Auto-execute code at exit? "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-12-11 17:09 +0100
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 08:18 -0800
Re: Auto-execute code at exit? "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-12-11 19:04 +0100
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 08:19 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 17:26 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 09:40 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 18:09 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 11:07 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 20:18 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 12:27 -0800
Re: Auto-execute code at exit? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-12-11 13:42 -0700
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 12:54 -0800
Re: Auto-execute code at exit? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-12-11 19:34 -0700
Re: Auto-execute code at exit? Melzzzzz <Melzzzzz@zzzzz.com> - 2017-12-11 17:46 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-11 19:31 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 18:48 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 09:36 +0100
Re: Auto-execute code at exit? gazelle@shell.xmission.com (Kenny McCormack) - 2017-12-11 18:49 +0000
Re: Auto-execute code at exit? scott@slp53.sl.home (Scott Lurndal) - 2017-12-11 20:33 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 12:39 -0800
Re: Auto-execute code at exit? scott@slp53.sl.home (Scott Lurndal) - 2017-12-11 21:22 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 13:25 -0800
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-12 05:45 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 21:00 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-11 13:13 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 21:45 +0000
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-12 10:46 +1300
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-11 14:04 -0800
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-12 05:42 -0800
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-11 13:53 -0800
Re: Auto-execute code at exit? scott@slp53.sl.home (Scott Lurndal) - 2017-12-11 21:21 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 21:53 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 08:01 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 18:00 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 11:01 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 20:44 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 12:52 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 21:16 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 13:24 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 09:55 +0100
Re: Auto-execute code at exit? Sjouke Burry <burrynulnulfour@ppllaanneett.nnll> - 2017-12-11 22:00 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 21:43 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 09:52 +0100
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-11 21:41 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 22:33 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-12 01:17 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-12 01:44 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 10:01 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-12 11:17 +0000
Re: Auto-execute code at exit? mark.bluemel@gmail.com - 2017-12-12 03:40 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-12 12:01 +0000
Re: Auto-execute code at exit? mark.bluemel@gmail.com - 2017-12-12 04:50 -0800
Re: Auto-execute code at exit? Gareth Owen <gwowen@gmail.com> - 2017-12-12 18:33 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-12 10:37 -0800
Re: Auto-execute code at exit? gazelle@shell.xmission.com (Kenny McCormack) - 2017-12-12 21:43 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-12 11:31 -0800
Re: Auto-execute code at exit? Gareth Owen <gwowen@gmail.com> - 2017-12-12 20:09 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 13:56 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-12 19:44 +0000
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-13 09:07 +1300
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 23:28 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 00:08 +0000
Re: Auto-execute code at exit? "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-12-13 01:42 +0100
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-13 16:35 +1300
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 10:55 +0000
Re: Auto-execute code at exit? Melzzzzz <Melzzzzz@zzzzz.com> - 2017-12-13 11:04 +0000
Re: Auto-execute code at exit? Robert Wessel <robertwessel2@yahoo.com> - 2017-12-13 11:45 -0600
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-13 13:36 +0100
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-14 07:34 +1300
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-13 03:20 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-13 11:25 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 11:50 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-13 14:27 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 14:31 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-13 16:56 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 19:27 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-13 21:15 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 22:48 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-14 07:44 +0100
Re: Auto-execute code at exit? Gareth Owen <gwowen@gmail.com> - 2017-12-14 06:55 +0000
Re: Auto-execute code at exit? mark.bluemel@gmail.com - 2017-12-14 00:32 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-15 00:01 +0000
Re: Auto-execute code at exit? mark.bluemel@gmail.com - 2017-12-15 00:48 -0800
Why post to Usenet? (Was: Auto-execute code at exit?) gazelle@shell.xmission.com (Kenny McCormack) - 2017-12-15 10:51 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-15 12:18 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-15 17:40 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-15 20:12 +0000
Re: Auto-execute code at exit? David Kleinecke <dkleinecke@gmail.com> - 2017-12-15 12:54 -0800
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-15 13:51 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-16 14:46 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-15 23:20 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-16 00:36 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-16 01:34 +0000
Re: Auto-execute code at exit? Manfred <noname@invalid.add> - 2017-12-16 20:06 +0100
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-17 17:33 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-17 21:35 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-17 15:06 -0800
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-18 12:41 +1300
Re: Auto-execute code at exit? Robert Wessel <robertwessel2@yahoo.com> - 2017-12-18 03:36 -0600
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-18 11:51 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-18 12:02 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-18 12:43 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-18 15:07 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-18 16:07 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-18 20:50 +0100
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-18 13:57 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-18 15:36 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-18 21:04 +0100
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-18 09:08 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-18 20:51 +0100
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-18 15:37 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-18 16:28 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-18 10:59 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-18 19:35 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-18 19:55 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-18 20:48 +0000
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-18 13:03 -0800
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-18 21:14 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 00:08 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-18 16:58 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 01:28 +0000
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-19 14:35 +1300
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 01:45 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-19 01:49 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 02:54 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-19 14:45 +0000
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-19 07:48 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 16:00 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-19 17:42 +0100
Re: Auto-execute code at exit? scott@slp53.sl.home (Scott Lurndal) - 2017-12-19 17:19 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-19 09:43 -0800
Re: Auto-execute code at exit? scott@slp53.sl.home (Scott Lurndal) - 2017-12-19 18:57 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-19 09:33 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 18:34 +0000
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-19 11:05 -0800
Re: Auto-execute code at exit? Manfred <noname@invalid.add> - 2017-12-18 21:09 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-18 20:38 +0000
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-19 13:35 +1300
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 01:00 +0000
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-19 14:04 +1300
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-20 13:42 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-20 15:52 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-20 15:42 +0000
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-20 08:16 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-20 18:25 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-20 10:48 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-20 20:43 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-20 12:44 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-21 15:18 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-21 09:45 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-21 20:08 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-21 12:33 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-21 22:42 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-21 15:20 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-22 09:57 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-22 08:21 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-23 13:32 +0100
Re: Auto-execute code at exit? Gareth Owen <gwowen@gmail.com> - 2017-12-23 19:35 +0000
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-26 12:08 -0800
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-26 12:36 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-27 10:38 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-27 08:14 -0800
Re: Auto-execute code at exit? Richard Damon <Richard@Damon-Family.org> - 2017-12-27 09:50 -0500
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-20 12:12 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-20 18:16 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-20 19:41 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-20 22:52 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-20 15:39 -0800
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-21 13:02 +1300
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-21 00:50 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-20 18:22 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-21 12:10 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-21 13:10 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-21 20:55 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-21 21:37 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-22 01:50 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-22 12:14 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-22 17:01 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-22 17:34 +0000
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-22 09:52 -0800
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-22 12:02 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-22 20:18 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-22 12:39 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-22 23:10 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-22 17:05 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-23 02:17 +0000
Re: Auto-execute code at exit? Richard Damon <Richard@Damon-Family.org> - 2017-12-22 22:14 -0500
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-23 14:43 +0100
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-23 14:31 +0100
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-24 09:45 +1300
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-23 16:28 +1300
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-23 11:23 +0000
Re: Auto-execute code at exit? Richard Damon <Richard@Damon-Family.org> - 2017-12-23 13:24 -0500
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-24 09:29 +1300
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-21 20:57 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-21 13:11 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-21 21:58 +0000
Re: Auto-execute code at exit? jameskuyper@verizon.net - 2017-12-21 14:03 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-22 01:34 +0000
Re: Auto-execute code at exit? jameskuyper@verizon.net - 2017-12-22 07:55 -0800
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-22 16:41 +0000
Re: Auto-execute code at exit? "James R. Kuyper" <jameskuyper@verizon.net> - 2017-12-22 12:46 -0500
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-23 11:57 +0000
Re: Auto-execute code at exit? James Kuyper <jameskuyper@verizon.net> - 2017-12-23 08:12 -0500
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-23 21:02 +0000
Re: Auto-execute code at exit? James Kuyper <jameskuyper@verizon.net> - 2017-12-23 16:13 -0500
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-23 22:15 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-23 14:45 -0800
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-23 15:47 -0800
Re: Auto-execute code at exit? James Kuyper <jameskuyper@verizon.net> - 2017-12-23 19:34 -0500
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-24 12:08 +0000
Re: Auto-execute code at exit? Melzzzzz <Melzzzzz@zzzzz.com> - 2017-12-24 12:11 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-24 12:17 +0000
Re: Auto-execute code at exit? jameskuyper@verizon.net - 2017-12-24 05:49 -0800
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-24 13:06 -0800
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-23 13:51 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-23 22:17 +0000
Re: Auto-execute code at exit? Gareth Owen <gwowen@gmail.com> - 2017-12-22 18:37 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-22 19:03 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-20 17:44 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-18 17:22 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 01:41 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-19 09:54 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-19 13:24 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-19 14:43 +0100
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-19 09:02 -0800
Re: Auto-execute code at exit? Manfred <noname@invalid.add> - 2017-12-18 20:58 +0100
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-18 22:36 +0100
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-18 20:37 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-18 09:13 -0800
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-18 20:51 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-18 09:03 -0800
Re: Auto-execute code at exit? Gareth Owen <gwowen@gmail.com> - 2017-12-18 19:13 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-18 11:28 -0800
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-18 10:07 +0100
Re: Auto-execute code at exit? supercat@casperkitty.com - 2017-12-18 07:50 -0800
Re: Auto-execute code at exit? Ian Collins <ian-news@hotmail.com> - 2017-12-16 12:21 +1300
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-15 09:51 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-14 12:08 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-14 05:13 -0800
Re: Auto-execute code at exit? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-12-13 09:21 -0700
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-13 19:27 +0100
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-13 15:14 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-13 17:11 +0100
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-13 00:29 +0000
Re: Auto-execute code at exit? mark.bluemel@gmail.com - 2017-12-13 00:41 -0800
Re: Auto-execute code at exit? Gareth Owen <gwowen@gmail.com> - 2017-12-14 06:51 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-14 14:40 +0000
Re: Auto-execute code at exit? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-12-14 17:15 +0000
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-14 18:59 +0000
Re: Auto-execute code at exit? David Brown <david.brown@hesbynett.no> - 2017-12-12 09:48 +0100
Re: Auto-execute code at exit? Melzzzzz <Melzzzzz@zzzzz.com> - 2017-12-11 17:40 +0000
Re: Auto-execute code at exit? Keith Thompson <kst-u@mib.org> - 2017-12-11 10:57 -0800
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-10 13:56 -0800
Re: Auto-execute code at exit? David Kleinecke <dkleinecke@gmail.com> - 2017-12-10 14:09 -0800
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-10 14:18 -0800
Re: Auto-execute code at exit? asetofsymbols@gmail.com - 2017-12-10 14:51 -0800
Re: Auto-execute code at exit? asetofsymbols@gmail.com - 2017-12-23 11:08 -0800
Re: Auto-execute code at exit? asetofsymbols@gmail.com - 2017-12-25 00:49 -0800
Re: Auto-execute code at exit? bartc <bc@freeuk.com> - 2017-12-11 00:29 +0000
Re: Auto-execute code at exit? Gareth Owen <gwowen@gmail.com> - 2017-12-11 18:30 +0000
Re: Auto-execute code at exit? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-11 11:09 -0800
Auto-execute code at exit? asetofsymbols@gmail.com - 2017-12-10 15:05 -0800
Re: Auto-execute code at exit? mcheung63@gmail.com - 2017-12-24 21:04 -0800
Page 4 of 16 — ← Prev page 1 2 3 [4] 5 6 … 16 Next page →
| From | bartc <bc@freeuk.com> |
|---|---|
| Date | 2017-12-11 17:26 +0000 |
| Message-ID | <6dzXB.219606$pG.106958@fx18.am4> |
| In reply to | #124140 |
On 11/12/2017 16:19, Rick C. Hodgin wrote: > On Monday, December 11, 2017 at 10:52:36 AM UTC-5, Bart wrote: >> The tricky bit is the stdout part. > > That shouldn't be tricky. Most OSes offer default handles which are > already defined for STDOUT, STDIN, and STDERR. You just push their > handle for the write. You can get a similar thing on Windows using GetStdHandle or some such function. Or even just create a file called "CON". But such a handle is not compatible with C file functions. Even if it was, the expression handle == stdout would still compare false. On Linux, it's a little easier because the OS, C, and the C runtime (and maybe POSIX; I'm not sure of its exact status) are all intertwined. (On my Linux, 'stdout' is an exported variable from a shared library libc.so.6, of type struct _IO_file* (same as *FILE). On Windows and in MSVC, 'stdout' is a macro equivalent to &__iob_func()[1]. __iob_func is a function with this signature: _CRTIMP FILE* __cdecl __iob_func(void); What was Melzzzzz saying about C having such a simple interface? Clearly 'stdout' is designed to be used primarily from actual C source code, otherwise its definition would be simpler and more independent from the implementation.) -- bartc
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2017-12-11 09:40 -0800 |
| Message-ID | <1977cbc1-916d-4915-8f2a-f29ba84fc332@googlegroups.com> |
| In reply to | #124144 |
On Monday, December 11, 2017 at 12:26:39 PM UTC-5, Bart wrote: > On 11/12/2017 16:19, Rick C. Hodgin wrote: > > On Monday, December 11, 2017 at 10:52:36 AM UTC-5, Bart wrote: > >> The tricky bit is the stdout part. > > > > That shouldn't be tricky. Most OSes offer default handles which are > > already defined for STDOUT, STDIN, and STDERR. You just push their > > handle for the write. > > You can get a similar thing on Windows using GetStdHandle or some such > function. Or even just create a file called "CON". I'm pretty sure DOS and Windows both automatically reserve file handles / descriptors for 0=stdin, 1=stdout, 2=stderr. So you can simply use those values without having to open anything. > But such a handle is not compatible with C file functions. Even if it > was, the expression handle == stdout would still compare false. > > On Linux, it's a little easier because the OS, C, and the C runtime (and > maybe POSIX; I'm not sure of its exact status) are all intertwined. > > (On my Linux, 'stdout' is an exported variable from a shared library > libc.so.6, of type struct _IO_file* (same as *FILE). > > On Windows and in MSVC, 'stdout' is a macro equivalent to > &__iob_func()[1]. __iob_func is a function with this signature: > > _CRTIMP FILE* __cdecl __iob_func(void); > > What was Melzzzzz saying about C having such a simple interface? Clearly > 'stdout' is designed to be used primarily from actual C source code, > otherwise its definition would be simpler and more independent from the > implementation.) I can test it later. Or you can now. :-) -- Rick C. Hodgin
[toc] | [prev] | [next] | [standalone]
| From | bartc <bc@freeuk.com> |
|---|---|
| Date | 2017-12-11 18:09 +0000 |
| Message-ID | <rRzXB.223669$GS.182962@fx06.am4> |
| In reply to | #124145 |
On 11/12/2017 17:40, Rick C. Hodgin wrote: > On Monday, December 11, 2017 at 12:26:39 PM UTC-5, Bart wrote: >> On 11/12/2017 16:19, Rick C. Hodgin wrote: >>> On Monday, December 11, 2017 at 10:52:36 AM UTC-5, Bart wrote: >>>> The tricky bit is the stdout part. >>> >>> That shouldn't be tricky. Most OSes offer default handles which are >>> already defined for STDOUT, STDIN, and STDERR. You just push their >>> handle for the write. >> >> You can get a similar thing on Windows using GetStdHandle or some such >> function. Or even just create a file called "CON". > > I'm pretty sure DOS and Windows both automatically reserve file > handles / descriptors for 0=stdin, 1=stdout, 2=stderr. So you > can simply use those values without having to open anything. Using 1 instead of stdout for fprintf, crashes. Not surprising as a pointer to a FILE object is expected. This comes up when you have a function (any function) that takes a file handle that will eventually be passed to a C file function. Sometimes the same function will be called with stdout (or stdin etc). Sometimes the function will need to compare the handle with stdout and do something different if it /is/ stdout. -- bartc
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2017-12-11 11:07 -0800 |
| Message-ID | <8e04d045-f697-46ec-bc1d-28da9ebf2f80@googlegroups.com> |
| In reply to | #124153 |
On Monday, December 11, 2017 at 1:09:37 PM UTC-5, Bart wrote:
> On 11/12/2017 17:40, Rick C. Hodgin wrote:
> > On Monday, December 11, 2017 at 12:26:39 PM UTC-5, Bart wrote:
> >> On 11/12/2017 16:19, Rick C. Hodgin wrote:
> >>> On Monday, December 11, 2017 at 10:52:36 AM UTC-5, Bart wrote:
> >>>> The tricky bit is the stdout part.
> >>>
> >>> That shouldn't be tricky. Most OSes offer default handles which are
> >>> already defined for STDOUT, STDIN, and STDERR. You just push their
> >>> handle for the write.
> >>
> >> You can get a similar thing on Windows using GetStdHandle or some such
> >> function. Or even just create a file called "CON".
> >
> > I'm pretty sure DOS and Windows both automatically reserve file
> > handles / descriptors for 0=stdin, 1=stdout, 2=stderr. So you
> > can simply use those values without having to open anything.
>
> Using 1 instead of stdout for fprintf, crashes. Not surprising as a
> pointer to a FILE object is expected.
What happens if you use this function passing in 1 and "rb+"?
FILE *fdopen(int fd, const char *mode);
> This comes up when you have a function (any function) that takes a file
> handle that will eventually be passed to a C file function.
>
> Sometimes the same function will be called with stdout (or stdin etc).
> Sometimes the function will need to compare the handle with stdout and
> do something different if it /is/ stdout.
--
Rick C. Hodgin
[toc] | [prev] | [next] | [standalone]
| From | bartc <bc@freeuk.com> |
|---|---|
| Date | 2017-12-11 20:18 +0000 |
| Message-ID | <8KBXB.300160$Wm2.230216@fx03.am4> |
| In reply to | #124166 |
On 11/12/2017 19:07, Rick C. Hodgin wrote:
> On Monday, December 11, 2017 at 1:09:37 PM UTC-5, Bart wrote:
>> Using 1 instead of stdout for fprintf, crashes. Not surprising as a
>> pointer to a FILE object is expected.
>
> What happens if you use this function passing in 1 and "rb+"?
>
> FILE *fdopen(int fd, const char *mode);
>
f=fdopen(1,"rb+");
gives me a handle that can be used to write to the console. But it has a
different value to stdout, so it's similar to using fopen("cons",...)
for that purpose.
--
bartc
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2017-12-11 12:27 -0800 |
| Message-ID | <0a44f803-297e-4f6e-a941-1d1a6da5a6e5@googlegroups.com> |
| In reply to | #124172 |
On Monday, December 11, 2017 at 3:18:33 PM UTC-5, Bart wrote:
> On 11/12/2017 19:07, Rick C. Hodgin wrote:
> > On Monday, December 11, 2017 at 1:09:37 PM UTC-5, Bart wrote:
>
> >> Using 1 instead of stdout for fprintf, crashes. Not surprising as a
> >> pointer to a FILE object is expected.
> >
> > What happens if you use this function passing in 1 and "rb+"?
> >
> > FILE *fdopen(int fd, const char *mode);
> >
>
> f=fdopen(1,"rb+");
>
> gives me a handle that can be used to write to the console. But it has a
> different value to stdout, so it's similar to using fopen("cons",...)
> for that purpose.
That's very interesting. I would attempt to load a C program into
PROCMON and see if it's actually making calls to create its own std*
file handles at startup, or if it is separately aliasing that code.
If you're doing it in Linux you could look a the source code for it.
FWIW, I think the way it appears to be working is an improper way
to do things. C apps should honor the OS handles, and without
translation or some kind of aliasing.
--
Rick C. Hodgin
[toc] | [prev] | [next] | [standalone]
| From | Joe Pfeiffer <pfeiffer@cs.nmsu.edu> |
|---|---|
| Date | 2017-12-11 13:42 -0700 |
| Message-ID | <1bd13lxagr.fsf@pfeifferfamily.net> |
| In reply to | #124174 |
"Rick C. Hodgin" <rick.c.hodgin@gmail.com> writes:
> On Monday, December 11, 2017 at 3:18:33 PM UTC-5, Bart wrote:
>> On 11/12/2017 19:07, Rick C. Hodgin wrote:
>> > On Monday, December 11, 2017 at 1:09:37 PM UTC-5, Bart wrote:
>>
>> >> Using 1 instead of stdout for fprintf, crashes. Not surprising as a
>> >> pointer to a FILE object is expected.
>> >
>> > What happens if you use this function passing in 1 and "rb+"?
>> >
>> > FILE *fdopen(int fd, const char *mode);
>> >
>>
>> f=fdopen(1,"rb+");
>>
>> gives me a handle that can be used to write to the console. But it has a
>> different value to stdout, so it's similar to using fopen("cons",...)
>> for that purpose.
>
> That's very interesting. I would attempt to load a C program into
> PROCMON and see if it's actually making calls to create its own std*
> file handles at startup, or if it is separately aliasing that code.
>
> If you're doing it in Linux you could look a the source code for it.
>
> FWIW, I think the way it appears to be working is an improper way
> to do things. C apps should honor the OS handles, and without
> translation or some kind of aliasing.
If you don't regard libc as a part of the OS (and I don't), you simply
won't have IO streams without a translation.
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2017-12-11 12:54 -0800 |
| Message-ID | <fdd647e9-c68d-4a3c-8166-58065d9c6ea2@googlegroups.com> |
| In reply to | #124179 |
On Monday, December 11, 2017 at 3:42:58 PM UTC-5, Joe Pfeiffer wrote:
> "Rick C. Hodgin" <rick.c.hodgin@gmail.com> writes:
>
> > On Monday, December 11, 2017 at 3:18:33 PM UTC-5, Bart wrote:
> >> On 11/12/2017 19:07, Rick C. Hodgin wrote:
> >> > On Monday, December 11, 2017 at 1:09:37 PM UTC-5, Bart wrote:
> >>
> >> >> Using 1 instead of stdout for fprintf, crashes. Not surprising as a
> >> >> pointer to a FILE object is expected.
> >> >
> >> > What happens if you use this function passing in 1 and "rb+"?
> >> >
> >> > FILE *fdopen(int fd, const char *mode);
> >> >
> >>
> >> f=fdopen(1,"rb+");
> >>
> >> gives me a handle that can be used to write to the console. But it has a
> >> different value to stdout, so it's similar to using fopen("cons",...)
> >> for that purpose.
> >
> > That's very interesting. I would attempt to load a C program into
> > PROCMON and see if it's actually making calls to create its own std*
> > file handles at startup, or if it is separately aliasing that code.
> >
> > If you're doing it in Linux you could look a the source code for it.
> >
> > FWIW, I think the way it appears to be working is an improper way
> > to do things. C apps should honor the OS handles, and without
> > translation or some kind of aliasing.
>
> If you don't regard libc as a part of the OS (and I don't), you simply
> won't have IO streams without a translation.
That's one thing I do not like about C. I believe C should have a
very solid recognition that it is running on real equipment, and is
connected to a real machine with a real OS. And from withing that
point of view, libc should acknowledge it is already home to an OS
with its own ways of doing things, and bend to meet them.
And if it wants to have its own way of doing things that is truly
isolated, then do so, but don't call it STDIN, STDOUT, STDERR, call
it CIN, COUT, CERR. Oh ... wait! :-)
--
Rick C. Hodgin
[toc] | [prev] | [next] | [standalone]
| From | Joe Pfeiffer <pfeiffer@cs.nmsu.edu> |
|---|---|
| Date | 2017-12-11 19:34 -0700 |
| Message-ID | <1b1sk0y8rj.fsf@pfeifferfamily.net> |
| In reply to | #124182 |
"Rick C. Hodgin" <rick.c.hodgin@gmail.com> writes:
> On Monday, December 11, 2017 at 3:42:58 PM UTC-5, Joe Pfeiffer wrote:
>> "Rick C. Hodgin" <rick.c.hodgin@gmail.com> writes:
>>
>> > On Monday, December 11, 2017 at 3:18:33 PM UTC-5, Bart wrote:
>> >> On 11/12/2017 19:07, Rick C. Hodgin wrote:
>> >> > On Monday, December 11, 2017 at 1:09:37 PM UTC-5, Bart wrote:
>> >>
>> >> >> Using 1 instead of stdout for fprintf, crashes. Not surprising as a
>> >> >> pointer to a FILE object is expected.
>> >> >
>> >> > What happens if you use this function passing in 1 and "rb+"?
>> >> >
>> >> > FILE *fdopen(int fd, const char *mode);
>> >> >
>> >>
>> >> f=fdopen(1,"rb+");
>> >>
>> >> gives me a handle that can be used to write to the console. But it has a
>> >> different value to stdout, so it's similar to using fopen("cons",...)
>> >> for that purpose.
>> >
>> > That's very interesting. I would attempt to load a C program into
>> > PROCMON and see if it's actually making calls to create its own std*
>> > file handles at startup, or if it is separately aliasing that code.
>> >
>> > If you're doing it in Linux you could look a the source code for it.
>> >
>> > FWIW, I think the way it appears to be working is an improper way
>> > to do things. C apps should honor the OS handles, and without
>> > translation or some kind of aliasing.
>>
>> If you don't regard libc as a part of the OS (and I don't), you simply
>> won't have IO streams without a translation.
>
> That's one thing I do not like about C. I believe C should have a
> very solid recognition that it is running on real equipment, and is
> connected to a real machine with a real OS. And from withing that
> point of view, libc should acknowledge it is already home to an OS
> with its own ways of doing things, and bend to meet them.
>
> And if it wants to have its own way of doing things that is truly
> isolated, then do so, but don't call it STDIN, STDOUT, STDERR, call
> it CIN, COUT, CERR. Oh ... wait! :-)
But the OS doesn't provide stdin, stdout, or stderr (it provides file
descriptors 0, 1, 2 in the case of a POSIX OS). Those are provided by
libc. stdin, stdout, and stderr *are* C's way of doing things that is
truly isolated.
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <Melzzzzz@zzzzz.com> |
|---|---|
| Date | 2017-12-11 17:46 +0000 |
| Message-ID | <p0mg9k$mf$2@news.albasani.net> |
| In reply to | #124140 |
On 2017-12-11, Rick C. Hodgin <rick.c.hodgin@gmail.com> wrote: > On Monday, December 11, 2017 at 10:52:36 AM UTC-5, Bart wrote: >> The tricky bit is the stdout part. > > That shouldn't be tricky. Most OSes offer default handles which are > already defined for STDOUT, STDIN, and STDERR. You just push their > handle for the write. > That's right, but we want fprintf ;) -- press any key to continue or any other to quit...
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2017-12-11 19:31 +0100 |
| Message-ID | <p0miue$rnm$1@dont-email.me> |
| In reply to | #124133 |
On 11/12/17 16:52, bartc wrote: > On 11/12/2017 15:42, David Brown wrote: >> On 11/12/17 16:33, bartc wrote: > >> <snip, including the joke at the end> > > Assuming you mean this, it wasn't a joke: > > (As a test, try and do the equivalent of: > > fprintf(stdout,"hello"); > > from assembly code for the platform of your choice.) > > The task is, given definitions for fprintf and stdout (it is assumed you > know how to do the actual mechanics of the call), how to write the code > from assembly. > > The tricky bit is the stdout part. > Yes, that was the bit I assumed was a joke - because it is /vastly/ easier to write in C than in assembly (unless you assume you have access to the C library from assembly, in which case it is merely /much/ easier to write in C). You moaned about how C has "a large amount of extra junk" and then showed how easy it is to write something in C. If it was /not/ a joke, then I am confused.
[toc] | [prev] | [next] | [standalone]
| From | bartc <bc@freeuk.com> |
|---|---|
| Date | 2017-12-11 18:48 +0000 |
| Message-ID | <DpAXB.173789$Am1.112814@fx23.am4> |
| In reply to | #124156 |
On 11/12/2017 18:31, David Brown wrote:
> On 11/12/17 16:52, bartc wrote:
>> On 11/12/2017 15:42, David Brown wrote:
>>> On 11/12/17 16:33, bartc wrote:
>>
>>> <snip, including the joke at the end>
>>
>> Assuming you mean this, it wasn't a joke:
>>
>> (As a test, try and do the equivalent of:
>>
>> fprintf(stdout,"hello");
>>
>> from assembly code for the platform of your choice.)
>>
>> The task is, given definitions for fprintf and stdout (it is assumed
>> you know how to do the actual mechanics of the call), how to write the
>> code from assembly.
>>
>> The tricky bit is the stdout part.
>>
>
> Yes, that was the bit I assumed was a joke - because it is /vastly/
> easier to write in C than in assembly (unless you assume you have access
> to the C library from assembly, in which case it is merely /much/ easier
> to write in C). You moaned about how C has "a large amount of extra
> junk" and then showed how easy it is to write something in C. If it was
> /not/ a joke, then I am confused.
>
The point of doing it in assembly is that you then /know/ that will
contain all the information needed to use it from anywhere else.
As it is, it vastly easier to write in C than ANY language [other than
C++], because that part of the library was designed to be used FROM C.
That suggests that, although is is used as a universal interface
language, it doesn't do the job as well as it could.
(At this moment, I haven't yet solved this problem, for my compiled
language, for stdout on Windows. The temporary solution I'm using is to
take the handle returned by 'fopen("con","wb")' and use that as stdout,
but it will not match the real stdout. I don't know how to create an
stderr equivalent.)
--
bartc
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2017-12-12 09:36 +0100 |
| Message-ID | <p0o4e4$vb6$1@dont-email.me> |
| In reply to | #124162 |
On 11/12/17 19:48, bartc wrote:
> On 11/12/2017 18:31, David Brown wrote:
>> On 11/12/17 16:52, bartc wrote:
>>> On 11/12/2017 15:42, David Brown wrote:
>>>> On 11/12/17 16:33, bartc wrote:
>>>
>>>> <snip, including the joke at the end>
>>>
>>> Assuming you mean this, it wasn't a joke:
>>>
>>> (As a test, try and do the equivalent of:
>>>
>>> fprintf(stdout,"hello");
>>>
>>> from assembly code for the platform of your choice.)
>>>
>>> The task is, given definitions for fprintf and stdout (it is assumed
>>> you know how to do the actual mechanics of the call), how to write
>>> the code from assembly.
>>>
>>> The tricky bit is the stdout part.
>>>
>>
>> Yes, that was the bit I assumed was a joke - because it is /vastly/
>> easier to write in C than in assembly (unless you assume you have
>> access to the C library from assembly, in which case it is merely
>> /much/ easier to write in C). You moaned about how C has "a large
>> amount of extra junk" and then showed how easy it is to write
>> something in C. If it was /not/ a joke, then I am confused.
>>
>
> The point of doing it in assembly is that you then /know/ that will
> contain all the information needed to use it from anywhere else.
>
Assembly code is either self-contained, or calls functions from
elsewhere. If that is a library rather than modules you wrote yourself,
then you need to understand the library's requirements to be sure you
have all the information needed to use it elsewhere.
With C, the situation is ... /exactly/ the same.
The C run-time library is a necessity for C - but you /know/ that, so it
is not an issue here. In fact it is much better than for assembly,
because you will usually need some sort of interface library if the
assembly is going to access OS services - but you don't know what that
library might be without looking at the linker scripts.
> As it is, it vastly easier to write in C than ANY language [other than
> C++], because that part of the library was designed to be used FROM C.
print "hello" in Python is quite easy. Dozens of languages have
something approximately the same as "printf". I don't see your point.
Calling C functions from other languages is usually extremely easy.
Most have a mechanism for accessing functions in dll's/so's, which will
always support C functions. And calling C functions from assembly is
also simple. (printf, being a variadic function, is one of the harder
examples. I have always thought that variadic functions were a mistake
in C.)
>
> That suggests that, although is is used as a universal interface
> language, it doesn't do the job as well as it could.
>
The rest of the world seems quite happy with it. I am sure it is not
/perfect/, but it does a pretty good job.
>
> (At this moment, I haven't yet solved this problem, for my compiled
> language, for stdout on Windows. The temporary solution I'm using is to
> take the handle returned by 'fopen("con","wb")' and use that as stdout,
> but it will not match the real stdout. I don't know how to create an
> stderr equivalent.)
>
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2017-12-11 18:49 +0000 |
| Message-ID | <p0mk07$ofl$1@news.xmission.com> |
| In reply to | #124156 |
In article <p0miue$rnm$1@dont-email.me>, David Brown <david.brown@hesbynett.no> wrote: ... >Yes, that was the bit I assumed was a joke - because it is /vastly/ >easier to write in C than in assembly (unless you assume you have access >to the C library from assembly, in which case it is merely /much/ easier >to write in C). You moaned about how C has "a large amount of extra >junk" and then showed how easy it is to write something in C. If it was >/not/ a joke, then I am confused. Total headcase. -- The randomly chosen signature file that would have appeared here is more than 4 lines long. As such, it violates one or more Usenet RFCs. In order to remain in compliance with said RFCs, the actual sig can be found at the following URL: http://user.xmission.com/~gazelle/Sigs/CLCtopics
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2017-12-11 20:33 +0000 |
| Message-ID | <vYBXB.11122$X82.1497@fx31.iad> |
| In reply to | #124156 |
David Brown <david.brown@hesbynett.no> writes:
>On 11/12/17 16:52, bartc wrote:
>> On 11/12/2017 15:42, David Brown wrote:
>>> On 11/12/17 16:33, bartc wrote:
>>
>>> <snip, including the joke at the end>
>>
>> Assuming you mean this, it wasn't a joke:
>>
>> (As a test, try and do the equivalent of:
>>
>> fprintf(stdout,"hello");
>>
.data
hw: .ascii "Hello World"
hwl: .long .-hw
.text
main:
mov $1, %rdx
movabs $hw, %rsi
mov hwl, %rdx
call write
xor %rax, %rax
ret
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2017-12-11 12:39 -0800 |
| Message-ID | <ce5e5714-db24-4d89-a893-1e02e8672803@googlegroups.com> |
| In reply to | #124176 |
On Monday, December 11, 2017 at 3:33:41 PM UTC-5, Scott Lurndal wrote: > David Brown <david.brown@hesbynett.no> writes: > >On 11/12/17 16:52, bartc wrote: > >> On 11/12/2017 15:42, David Brown wrote: > >>> On 11/12/17 16:33, bartc wrote: > >> > >>> <snip, including the joke at the end> > >> > >> Assuming you mean this, it wasn't a joke: > >> > >> (As a test, try and do the equivalent of: > >> > >> fprintf(stdout,"hello"); > >> > > .data > hw: .ascii "Hello World" > hwl: .long .-hw > .text > main: > mov $1, %rdx > movabs $hw, %rsi > mov hwl, %rdx > call write > xor %rax, %rax > ret Until you're willing to use Intel syntax, Scott, I can no longer communicate with you. Be gone AT&T and your vile obfuscation. :-) -- Rick C. Hodgin
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2017-12-11 21:22 +0000 |
| Message-ID | <%FCXB.12150$603.9594@fx16.iad> |
| In reply to | #124178 |
"Rick C. Hodgin" <rick.c.hodgin@gmail.com> writes: > >Until you're willing to use Intel syntax, Scott, I can no longer >communicate with you. Good. Get thee behind me.
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2017-12-11 13:25 -0800 |
| Message-ID | <7472e848-98d7-4579-a5a7-9c9f71193c07@googlegroups.com> |
| In reply to | #124188 |
On Monday, December 11, 2017 at 4:22:12 PM UTC-5, Scott Lurndal wrote:
> "Rick C. Hodgin" <rick.c.hodgin@gmail.com> writes:
>
> >
> >Until you're willing to use Intel syntax, Scott, I can no longer
> >communicate with you.
>
> Good. Get thee behind me.
Know you nothing of humor, good Scott?
--
Rick C. Hodgin
PS - I would've called you "great Scott," but I feared it might
confuse you (what with the exclamation existing and all).
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2017-12-12 05:45 -0800 |
| Message-ID | <7d63d2ed-b43d-43b4-8a77-1891ce23bfdc@googlegroups.com> |
| In reply to | #124188 |
On Monday, December 11, 2017 at 4:22:12 PM UTC-5, Scott Lurndal wrote: > "Rick C. Hodgin" <rick.c.hodgin@gmail.com> writes: > > > > >Until you're willing to use Intel syntax, Scott, I can no longer > >communicate with you. > > Good. Get thee behind me. I hope you realize I respect and admire your skill set, Scott. I think you are brash and harsh in your replies to people at times, but there are other posts which are solidly informative and teaching. There are no doubts regarding your skills and abilities. When I write things like "Until you're willing to use Intel syntax..." I am only joking around being silly ... as men do one to another. -- Rick C. Hodgin
[toc] | [prev] | [next] | [standalone]
| From | bartc <bc@freeuk.com> |
|---|---|
| Date | 2017-12-11 21:00 +0000 |
| Message-ID | <ilCXB.136539$mn.13540@fx29.am4> |
| In reply to | #124176 |
On 11/12/2017 20:33, Scott Lurndal wrote:
> David Brown <david.brown@hesbynett.no> writes:
>> On 11/12/17 16:52, bartc wrote:
>>> On 11/12/2017 15:42, David Brown wrote:
>>>> On 11/12/17 16:33, bartc wrote:
>>>
>>>> <snip, including the joke at the end>
>>>
>>> Assuming you mean this, it wasn't a joke:
>>>
>>> (As a test, try and do the equivalent of:
>>>
>>> Â fprintf(stdout,"hello");
>>>
>
> .data
> hw: .ascii "Hello World"
> hwl: .long .-hw
> .text
> main:
> mov $1, %rdx
> movabs $hw, %rsi
> mov hwl, %rdx
> call write
> xor %rax, %rax
> ret
This doesn't call fprintf.
And it doesn't use stdout. (And it writes the wrong message...)
In my language, if I write:
println a,b,c
println @f,a,b,c
Then I get these two different lines when translated to C:
printf("%f %f %f\n",a,b,c);
fprintf(f,"%f %f %f\n",a,b,c);
That's workable. But supposed I wanted to write, in the source language:
println @f,a,b,c
where f could be a file handle, or it could refer to the console (ie.
stdout or stderr). That would be translated as fprintf. But the f
argument needs to be stdout or equivalent.
This is where this comes up. I can get something that would probably
work, but that won't match a real stdout. Or, if output from this fake
stdout is interpersed with that from a real stdout, I don't know what
interactions there could be.
The real problem is that stdout etc are defined in a way that is not
conducive to their use from outside the language.
--
bartc
[toc] | [prev] | [next] | [standalone]
Page 4 of 16 — ← Prev page 1 2 3 [4] 5 6 … 16 Next page →
Back to top | Article view | comp.lang.c
csiph-web