Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #124149 > unrolled thread
| Started by | Wuns Haerst <Wuns.Haerst@wurstfabrik.at> |
|---|---|
| First post | 2026-06-30 10:27 +0200 |
| Last post | 2026-07-17 15:23 +0300 |
| Articles | 20 on this page of 195 — 15 participants |
Back to article view | Back to comp.lang.c++
How to inline the main function of a thread? Wuns Haerst <Wuns.Haerst@wurstfabrik.at> - 2026-06-30 10:27 +0200
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-06-30 01:42 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-06-30 10:44 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-01 12:23 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-02 08:13 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-02 11:41 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-03 08:59 +0000
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-03 14:41 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-03 15:59 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-05 13:22 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-06 09:29 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-06 12:31 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-07 10:41 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-07 15:30 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-08 09:38 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-08 14:13 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-03 12:44 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-03 12:45 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-04 09:16 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-04 17:32 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-04 17:35 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-05 08:19 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-05 01:21 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-05 15:48 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-05 13:01 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-06 09:28 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-06 21:42 +0300
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-06 12:45 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-06 12:53 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-07 15:07 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-07 10:40 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-07 20:36 +0300
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-07 18:09 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-07 21:40 +0300
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-07 22:11 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-08 09:34 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-08 22:16 +0300
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-08 14:16 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-09 08:55 +0000
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-09 15:18 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-09 15:43 +0000
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-10 15:32 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 16:03 +0000
Re: How to inline the main function of a thread? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-07-09 14:07 -0700
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-10 15:34 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-09 22:15 +0300
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 09:21 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-10 14:02 +0300
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 11:22 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-10 14:45 +0300
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 15:12 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-10 18:43 +0300
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 16:06 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-10 19:13 +0300
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-11 09:28 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-11 14:41 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-12 15:23 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-13 13:12 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-14 11:05 +0000
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-14 14:31 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-14 15:42 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-10 15:33 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-10 15:33 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-08 14:15 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-09 08:55 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-09 12:51 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 09:22 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-10 14:22 +0300
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 11:24 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-10 12:32 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-11 09:29 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-11 14:09 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-12 15:15 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-12 10:58 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-13 09:39 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-13 13:14 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-05 13:16 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-06 09:29 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-06 12:49 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-07 10:41 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-07 15:17 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-08 09:38 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-08 14:17 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-09 08:56 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-09 12:53 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 09:24 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-10 13:36 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-11 09:30 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-11 14:08 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-07 15:19 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-04 23:36 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-05 08:21 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-05 01:22 -0700
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-05 14:39 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-05 15:50 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-12 11:22 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-05 15:49 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-10 00:16 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-10 09:25 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-10 15:36 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-11 09:32 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-11 14:10 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-12 15:18 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-12 11:21 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-13 10:26 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-13 13:05 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-14 10:58 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-14 13:45 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-15 11:23 +0000
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-15 14:07 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-15 15:54 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-15 15:51 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-16 10:44 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-16 12:37 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-17 09:26 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-17 13:32 +0300
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-17 12:00 -0700
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-18 23:12 +0300
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-18 17:15 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-18 17:18 -0700
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-19 04:56 +0300
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-19 05:00 +0300
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-19 13:54 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-19 07:57 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-19 13:54 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-19 13:57 -0700
Re: How to inline the main function of a thread? boltar@battlestar-galactica.com - 2026-07-20 07:51 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-20 13:15 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-18 17:37 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-16 12:40 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-17 09:27 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-19 13:55 -0700
Re: How to inline the main function of a thread? boltar@battlestar-galactica.com - 2026-07-20 07:49 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-20 13:16 -0700
Re: How to inline the main function of a thread? boltar@battlestar-galactica.com - 2026-07-21 15:55 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-21 13:47 -0700
Re: How to inline the main function of a thread? boltar@battlestar-galactica.com - 2026-07-21 21:13 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-21 14:28 -0700
Re: How to inline the main function of a thread? boltar@battlestar.co.uk - 2026-07-22 08:01 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-22 13:28 -0700
Re: How to inline the main function of a thread? boltar@battlestar.co.uk - 2026-07-23 15:01 +0000
Re: How to inline the main function of a thread? cross@spitfire.i.gajendra.net (Dan Cross) - 2026-07-22 01:53 +0000
Re: How to inline the main function of a thread? boltar@battlestar.co.uk - 2026-07-22 08:02 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-22 13:30 -0700
Re: How to inline the main function of a thread? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-07-22 16:02 -0700
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-23 15:00 +0000
Re: How to inline the main function of a thread? boltar@caprica.space - 2026-07-23 15:05 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-11 14:11 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-12 15:19 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-12 11:02 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-13 09:42 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-16 13:50 -0700
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-12 23:05 +0300
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-13 13:08 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-16 13:56 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-16 13:58 -0700
Re: How to inline the main function of a thread? Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-07-03 10:45 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-03 12:36 -0700
Re: How to inline the main function of a thread? Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-07-28 12:50 +0100
Re: How to inline the main function of a thread? David Brown <david.brown@hesbynett.no> - 2026-06-30 11:07 +0200
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-06-30 10:46 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-01 12:25 -0700
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-02 08:13 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-06-30 10:41 +0000
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-06-30 14:14 +0000
Re: How to inline the main function of a thread? Bonita Montero <Bonita.Montero@gmail.com> - 2026-06-30 16:30 +0200
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-06-30 15:25 +0000
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-01 12:30 -0700
Re: How to inline the main function of a thread? Bonita Montero <Bonita.Montero@gmail.com> - 2026-07-05 14:03 +0200
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-05 14:41 +0000
Re: How to inline the main function of a thread? Bonita Montero <Bonita.Montero@gmail.com> - 2026-07-05 20:08 +0200
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-05 13:05 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-05 14:03 -0700
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-05 14:36 -0700
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-07-06 17:47 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-06 21:49 +0300
Re: How to inline the main function of a thread? Bonita Montero <Bonita.Montero@gmail.com> - 2026-07-08 15:47 +0200
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-08 14:32 -0700
Re: How to inline the main function of a thread? Bonita Montero <Bonita.Montero@gmail.com> - 2026-07-09 10:34 +0200
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-09 13:01 -0700
Re: How to inline the main function of a thread? Bonita Montero <Bonita.Montero@gmail.com> - 2026-07-10 05:58 +0200
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-12 11:19 -0700
Re: How to inline the main function of a thread? Bonita Montero <Bonita.Montero@gmail.com> - 2026-07-17 13:56 +0200
Re: How to inline the main function of a thread? Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-07-28 13:31 +0100
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-06-30 15:39 +0000
Re: How to inline the main function of a thread? Wuns Haerst <Wuns.Haerst@wurstfabrik.at> - 2026-06-30 18:00 +0200
Re: How to inline the main function of a thread? scott@slp53.sl.home (Scott Lurndal) - 2026-06-30 17:05 +0000
Re: How to inline the main function of a thread? boltar@caprica.universe - 2026-07-01 08:22 +0000
Re: How to inline the main function of a thread? Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-07-28 14:43 +0100
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-28 12:31 -0700
Re: How to inline the main function of a thread? boltar@uxvz2mpj0o8fzg70vyzzcf46nvx2.biz - 2026-07-29 08:36 +0000
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-06-30 23:29 +0300
Re: How to inline the main function of a thread? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-04 23:47 -0700
Re: How to inline the main function of a thread? Wuns Haerst <Wuns.Haerst@wurstfabrik.at> - 2026-07-17 13:45 +0200
Re: How to inline the main function of a thread? Michael S <already5chosen@yahoo.com> - 2026-07-17 15:23 +0300
Page 8 of 10 — ← Prev page 1 … 6 7 [8] 9 10 Next page →
| From | boltar@battlestar.co.uk |
|---|---|
| Date | 2026-07-23 15:01 +0000 |
| Message-ID | <113tac1$38ade$1@dont-email.me> |
| In reply to | #124359 |
On Wed, 22 Jul 2026 13:28:46 -0700 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote: >On 7/22/2026 1:01 AM, boltar@battlestar.co.uk wrote: >> On Tue, 21 Jul 2026 14:28:43 -0700 >> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote: >>> On 7/21/2026 2:13 PM, boltar@battlestar-galactica.com wrote: >>>> I don't care about the kernel implementation, I'm talking about the >>>> userspace >>>> side. I'd have thought that was obvious. >>>> >>> >>> But the userspace side wrt sockets needs to work with the kernel side. >> >> Are you an LLM? You seem to understand the meaning of words but get lost >> on the meaning of the whole post. >> > >No LLM, I have a long history on this group. > >You are the one that seems be be missing something... As if you no >experience with using sockets? Oh you are funny :) FYI wrote my first program using sockets in 1992 and amongst other things I've written line handlers for a number of stock exchanges. Just because you know nothing about unix sockets API and are firmly stuck in win32 don't assume everyone else is an idiot.
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2026-07-22 01:53 +0000 |
| Message-ID | <113p7qp$nu2$1@reader1.panix.com> |
| In reply to | #124352 |
In article <113ond3$2ncgf$1@dont-email.me>, <boltar@battlestar-galactica.com> wrote: >On Tue, 21 Jul 2026 13:47:34 -0700 >"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote: >>On 7/21/2026 8:55 AM, boltar@battlestar-galactica.com wrote: >>> On Mon, 20 Jul 2026 13:16:54 -0700 >>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote: >>>> On 7/20/2026 12:49 AM, boltar@battlestar-galactica.com wrote: >>>>> On Sun, 19 Jul 2026 13:55:37 -0700 >>>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote: >>>>>> On 7/17/2026 2:27 AM, boltar@caprica.universe wrote: >>>>>>> No idea, I'm not a win32 developer. Windows seems to make a >>>>>>> complete meal >>>>>>> out of what should be - in userspace - a simple process. >>>>>>> >>>>>> >>>>>> Make your own OS and show them how its done. ;^) >>>>> >>>>> I dont need to - thomson and Richie did it in 1969. >>>>> >>>> >>>> Well, patch the linux kernel, or the winnt kernel, and show them how >>>> you make use of your new socket infrastructure? >>> >>> I don't follow. All I'm saying is while its not perfect, the unix - and >>> later >>> posix - socket model is reasonably simple and dovetails nicely with other >>> file descriptor based user subsystems. The only addition I would make is to >>> make AF_INET sockets visible in the filesystem just like AF_UNIX ones. >>> >> >>But, you are telling us how it should work, when you don't know how it >>does work? > >I don't care about the kernel implementation, I'm talking about the userspace >side. I'd have thought that was obvious. Would you mind not changing your `From:` header, so that those of us who have plonked you don't have to keep updating our configurations? Thanks. - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | boltar@battlestar.co.uk |
|---|---|
| Date | 2026-07-22 08:02 +0000 |
| Message-ID | <113pteu$35p8s$1@dont-email.me> |
| In reply to | #124354 |
On Wed, 22 Jul 2026 01:53:29 -0000 (UTC) cross@spitfire.i.gajendra.net (Dan Cross) wrote: >In article <113ond3$2ncgf$1@dont-email.me>, >>I don't care about the kernel implementation, I'm talking about the userspace >>side. I'd have thought that was obvious. > >Would you mind not changing your `From:` header, so that those >of us who have plonked you don't have to keep updating our >configurations? Thanks. Why, are you afraid of learning something because it hurts?
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-07-22 13:30 -0700 |
| Message-ID | <113r98m$396f7$3@dont-email.me> |
| In reply to | #124357 |
On 7/22/2026 1:02 AM, boltar@battlestar.co.uk wrote: > On Wed, 22 Jul 2026 01:53:29 -0000 (UTC) > cross@spitfire.i.gajendra.net (Dan Cross) wrote: >> In article <113ond3$2ncgf$1@dont-email.me>, >>> I don't care about the kernel implementation, I'm talking about the userspace >>> side. I'd have thought that was obvious. >> >> Would you mind not changing your `From:` header, so that those >> of us who have plonked you don't have to keep updating our >> configurations? Thanks. > > Why, are you afraid of learning something because it hurts? > rofl. You are trolling! Never mind. Fell into your trap. Sorry.
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2026-07-22 16:02 -0700 |
| Message-ID | <113ri5l$3b8mk$2@kst.eternal-september.org> |
| In reply to | #124357 |
boltar@battlestar.co.uk writes:
> On Wed, 22 Jul 2026 01:53:29 -0000 (UTC)
> cross@spitfire.i.gajendra.net (Dan Cross) wrote:
>>In article <113ond3$2ncgf$1@dont-email.me>,
>>>I don't care about the kernel implementation, I'm talking about the userspace
>>>side. I'd have thought that was obvious.
>>
>>Would you mind not changing your `From:` header, so that those
>>of us who have plonked you don't have to keep updating our
>>configurations? Thanks.
>
> Why, are you afraid of learning something because it hurts?
I won't speak for Dan, but since I've decided I don't want to read
what you write (a decision I'm not required or inclined to explain),
deliberately bypassing my filters is extremely rude.
I currently have 4 variants of your posting address in my killfile,
about to be 5. You appear to think that your judgement about whether
I should read your posts is more important than mine. You're wrong.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2026-07-23 15:00 +0000 |
| Message-ID | <B0q8S.176605$XTrf.139743@fx15.iad> |
| In reply to | #124361 |
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes: >boltar@battlestar.co.uk writes: >> On Wed, 22 Jul 2026 01:53:29 -0000 (UTC) >> cross@spitfire.i.gajendra.net (Dan Cross) wrote: >>>In article <113ond3$2ncgf$1@dont-email.me>, >>>>I don't care about the kernel implementation, I'm talking about the userspace >>>>side. I'd have thought that was obvious. >>> >>>Would you mind not changing your `From:` header, so that those >>>of us who have plonked you don't have to keep updating our >>>configurations? Thanks. >> >> Why, are you afraid of learning something because it hurts? > >I won't speak for Dan, but since I've decided I don't want to read >what you write (a decision I'm not required or inclined to explain), >deliberately bypassing my filters is extremely rude. > >I currently have 4 variants of your posting address in my killfile, >about to be 5. You appear to think that your judgement about whether >I should read your posts is more important than mine. You're wrong. Indeed, agreed. I'll note that "Gaius Baltar" in the Battlestar Galactica series was considered "weak", "arrogant" and "a coward"; narcissistic, self-centered, feckless and vain (https://en.wikipedia.org/wiki/Gaius_Baltar). The poster using that identity here seems to have embraced those characteristics, rather than the humble version that the fictional character later became.
[toc] | [prev] | [next] | [standalone]
| From | boltar@caprica.space |
|---|---|
| Date | 2026-07-23 15:05 +0000 |
| Message-ID | <113tajf$3ua7q$1@dont-email.me> |
| In reply to | #124361 |
On Wed, 22 Jul 2026 16:02:13 -0700 Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote: >boltar@battlestar.co.uk writes: >> Why, are you afraid of learning something because it hurts? > >I won't speak for Dan, but since I've decided I don't want to read >what you write (a decision I'm not required or inclined to explain), >deliberately bypassing my filters is extremely rude. Oh please, this isn't 1985. I'll tell you what rude is - killfiling someone, hand waving away the reason then acting all hurt and wounded when you accidentaly read their post. Well diddums. >I currently have 4 variants of your posting address in my killfile, >about to be 5. You appear to think that your judgement about whether >I should read your posts is more important than mine. You're wrong. I can make it 5000 if you like. The from address on this server is freeform and bears no relation to the account address.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-07-11 14:11 -0700 |
| Message-ID | <112ubhj$2bfoi$4@dont-email.me> |
| In reply to | #124278 |
On 7/11/2026 2:32 AM, boltar@caprica.universe wrote: > On Fri, 10 Jul 2026 15:36:42 -0700 > "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >> On 7/10/2026 2:25 AM, boltar@caprica.universe wrote: >>> On Fri, 10 Jul 2026 00:16:41 -0700 >>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>> On 7/5/2026 8:49 AM, boltar@caprica.universe wrote: >>>>> Why? Once its down a socket - in unix - is just an integer pointing >>>>> to nothing. >>>>> What difference does it make if the same value gets reused? >>>>> >>>> >>>> TF_REUSE_SOCKET allows one to reuse a socket in a more efficient >>>> way. DisconnectEx. Fairly nice! Avoid calling WSASocket again. >>> >>> Sounds like win32 is a whole other world. Thank god I never had to >>> both with it. >>> >> >> Fair enough. Reusing a socket is nothing new, right? > > On *nix a socket is simply a integer key into the lower level networking > subsystem. Re-using once the link it was the key for has been closed > makes no sense. You may well get the same integer value if you close a > socket then > open a new one but its irrelevant. > After a DisconnctEx returns successfully, the socket in question can be reused for AcceptEx or ConnectEx. No need to call WSASocket to make a new one.
[toc] | [prev] | [next] | [standalone]
| From | boltar@caprica.universe |
|---|---|
| Date | 2026-07-12 15:19 +0000 |
| Message-ID | <1130bao$2tql2$1@dont-email.me> |
| In reply to | #124282 |
On Sat, 11 Jul 2026 14:11:15 -0700 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >On 7/11/2026 2:32 AM, boltar@caprica.universe wrote: >> On Fri, 10 Jul 2026 15:36:42 -0700 >> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>> On 7/10/2026 2:25 AM, boltar@caprica.universe wrote: >>>> On Fri, 10 Jul 2026 00:16:41 -0700 >>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>>> On 7/5/2026 8:49 AM, boltar@caprica.universe wrote: >>>>>> Why? Once its down a socket - in unix - is just an integer pointing >>>>>> to nothing. >>>>>> What difference does it make if the same value gets reused? >>>>>> >>>>> >>>>> TF_REUSE_SOCKET allows one to reuse a socket in a more efficient >>>>> way. DisconnectEx. Fairly nice! Avoid calling WSASocket again. >>>> >>>> Sounds like win32 is a whole other world. Thank god I never had to >>>> both with it. >>>> >>> >>> Fair enough. Reusing a socket is nothing new, right? >> >> On *nix a socket is simply a integer key into the lower level networking >> subsystem. Re-using once the link it was the key for has been closed >> makes no sense. You may well get the same integer value if you close a >> socket then >> open a new one but its irrelevant. >> > >After a DisconnctEx returns successfully, the socket in question can be >reused for AcceptEx or ConnectEx. No need to call WSASocket to make a >new one. Seems WSASocket() returns a structure with a whole load of crap in it unlike posix socket() which returns an int. So maybe in win32 it does make sense.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-07-12 11:02 -0700 |
| Message-ID | <1130ksd$30s27$2@dont-email.me> |
| In reply to | #124286 |
On 7/12/2026 8:19 AM, boltar@caprica.universe wrote: > On Sat, 11 Jul 2026 14:11:15 -0700 > "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >> On 7/11/2026 2:32 AM, boltar@caprica.universe wrote: >>> On Fri, 10 Jul 2026 15:36:42 -0700 >>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>> On 7/10/2026 2:25 AM, boltar@caprica.universe wrote: >>>>> On Fri, 10 Jul 2026 00:16:41 -0700 >>>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>>>> On 7/5/2026 8:49 AM, boltar@caprica.universe wrote: >>>>>>> Why? Once its down a socket - in unix - is just an integer >>>>>>> pointing to nothing. >>>>>>> What difference does it make if the same value gets reused? >>>>>>> >>>>>> >>>>>> TF_REUSE_SOCKET allows one to reuse a socket in a more efficient >>>>>> way. DisconnectEx. Fairly nice! Avoid calling WSASocket again. >>>>> >>>>> Sounds like win32 is a whole other world. Thank god I never had to >>>>> both with it. >>>>> >>>> >>>> Fair enough. Reusing a socket is nothing new, right? >>> >>> On *nix a socket is simply a integer key into the lower level networking >>> subsystem. Re-using once the link it was the key for has been closed >>> makes no sense. You may well get the same integer value if you close >>> a socket then >>> open a new one but its irrelevant. >>> >> >> After a DisconnctEx returns successfully, the socket in question can >> be reused for AcceptEx or ConnectEx. No need to call WSASocket to make >> a new one. > > Seems WSASocket() returns a structure with a whole load of crap in it > unlike > posix socket() which returns an int. So maybe in win32 it does make sense. > Well, it creates a socket. Why go through all of that logic when the socket is in a state that allows for reuse anyway?
[toc] | [prev] | [next] | [standalone]
| From | boltar@caprica.universe |
|---|---|
| Date | 2026-07-13 09:42 +0000 |
| Message-ID | <1132btq$2ovlt$1@dont-email.me> |
| In reply to | #124289 |
On Sun, 12 Jul 2026 11:02:53 -0700 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >On 7/12/2026 8:19 AM, boltar@caprica.universe wrote: >> On Sat, 11 Jul 2026 14:11:15 -0700 >> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>> On 7/11/2026 2:32 AM, boltar@caprica.universe wrote: >>>> On Fri, 10 Jul 2026 15:36:42 -0700 >>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>>> On 7/10/2026 2:25 AM, boltar@caprica.universe wrote: >>>>>> On Fri, 10 Jul 2026 00:16:41 -0700 >>>>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>>>>> On 7/5/2026 8:49 AM, boltar@caprica.universe wrote: >>>>>>>> Why? Once its down a socket - in unix - is just an integer >>>>>>>> pointing to nothing. >>>>>>>> What difference does it make if the same value gets reused? >>>>>>>> >>>>>>> >>>>>>> TF_REUSE_SOCKET allows one to reuse a socket in a more efficient >>>>>>> way. DisconnectEx. Fairly nice! Avoid calling WSASocket again. >>>>>> >>>>>> Sounds like win32 is a whole other world. Thank god I never had to >>>>>> both with it. >>>>>> >>>>> >>>>> Fair enough. Reusing a socket is nothing new, right? >>>> >>>> On *nix a socket is simply a integer key into the lower level networking >>>> subsystem. Re-using once the link it was the key for has been closed >>>> makes no sense. You may well get the same integer value if you close >>>> a socket then >>>> open a new one but its irrelevant. >>>> >>> >>> After a DisconnctEx returns successfully, the socket in question can >>> be reused for AcceptEx or ConnectEx. No need to call WSASocket to make >>> a new one. >> >> Seems WSASocket() returns a structure with a whole load of crap in it >> unlike >> posix socket() which returns an int. So maybe in win32 it does make sense. >> > >Well, it creates a socket. Why go through all of that logic when the >socket is in a state that allows for reuse anyway? I guess it depends on how its implemented internally. It would seem to me that the vast majority of the time and effort by the kernel in any OS is setting up and tearing down connections, creating a structure in userspace is probably a fraction of that and plus userspace structures would require field validity checks each time its used whereis with an int its either valid or it isn't.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-07-16 13:50 -0700 |
| Message-ID | <113bg5r$29gss$1@dont-email.me> |
| In reply to | #124295 |
On 7/13/2026 2:42 AM, boltar@caprica.universe wrote: > On Sun, 12 Jul 2026 11:02:53 -0700 > "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >> On 7/12/2026 8:19 AM, boltar@caprica.universe wrote: >>> On Sat, 11 Jul 2026 14:11:15 -0700 >>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>> On 7/11/2026 2:32 AM, boltar@caprica.universe wrote: >>>>> On Fri, 10 Jul 2026 15:36:42 -0700 >>>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>>>> On 7/10/2026 2:25 AM, boltar@caprica.universe wrote: >>>>>>> On Fri, 10 Jul 2026 00:16:41 -0700 >>>>>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>>>>>> On 7/5/2026 8:49 AM, boltar@caprica.universe wrote: >>>>>>>>> Why? Once its down a socket - in unix - is just an integer >>>>>>>>> pointing to nothing. >>>>>>>>> What difference does it make if the same value gets reused? >>>>>>>>> >>>>>>>> >>>>>>>> TF_REUSE_SOCKET allows one to reuse a socket in a more efficient >>>>>>>> way. DisconnectEx. Fairly nice! Avoid calling WSASocket again. >>>>>>> >>>>>>> Sounds like win32 is a whole other world. Thank god I never had >>>>>>> to both with it. >>>>>>> >>>>>> >>>>>> Fair enough. Reusing a socket is nothing new, right? >>>>> >>>>> On *nix a socket is simply a integer key into the lower level >>>>> networking >>>>> subsystem. Re-using once the link it was the key for has been >>>>> closed makes no sense. You may well get the same integer value if >>>>> you close a socket then >>>>> open a new one but its irrelevant. >>>>> >>>> >>>> After a DisconnctEx returns successfully, the socket in question can >>>> be reused for AcceptEx or ConnectEx. No need to call WSASocket to >>>> make a new one. >>> >>> Seems WSASocket() returns a structure with a whole load of crap in it >>> unlike >>> posix socket() which returns an int. So maybe in win32 it does make >>> sense. >>> >> >> Well, it creates a socket. Why go through all of that logic when the >> socket is in a state that allows for reuse anyway? > > I guess it depends on how its implemented internally. Indeed it does. Its a kernel call, and does some things. Avoid calling closesocket and then socket again! Also, think of what can occur. Say we want a graceful shutdown. shutdown(SD_SEND), wait for a zero byte recv, or whatever. If we can reuse that socket for an accept or connect, well, GOOD! Why would I call closesocket on it when I don't have to. Actually, reusing sockets is part of POSIX with some flags. Perhaps not as fine grain as Windows, but whatever. > It would seem to > me that > the vast majority of the time and effort by the kernel in any OS is setting > up and tearing down connections, creating a structure in userspace is > probably a fraction of that and plus userspace structures would require > field validity checks each time its used whereis with an int its either > valid or it isn't. > Its more than that. It works with the kernel as well.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2026-07-12 23:05 +0300 |
| Message-ID | <20260712230549.00006a20@yahoo.com> |
| In reply to | #124286 |
On Sun, 12 Jul 2026 15:19:52 -0000 (UTC) boltar@caprica.universe wrote: > On Sat, 11 Jul 2026 14:11:15 -0700 > "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: > >On 7/11/2026 2:32 AM, boltar@caprica.universe wrote: > >> On Fri, 10 Jul 2026 15:36:42 -0700 > >> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: > >>> On 7/10/2026 2:25 AM, boltar@caprica.universe wrote: > >>>> On Fri, 10 Jul 2026 00:16:41 -0700 > >>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: > >>>>> On 7/5/2026 8:49 AM, boltar@caprica.universe wrote: > >>>>>> Why? Once its down a socket - in unix - is just an integer > >>>>>> pointing to nothing. > >>>>>> What difference does it make if the same value gets reused? > >>>>>> > >>>>> > >>>>> TF_REUSE_SOCKET allows one to reuse a socket in a more > >>>>> efficient way. DisconnectEx. Fairly nice! Avoid calling > >>>>> WSASocket again. > >>>> > >>>> Sounds like win32 is a whole other world. Thank god I never had > >>>> to both with it. > >>>> > >>> > >>> Fair enough. Reusing a socket is nothing new, right? > >> > >> On *nix a socket is simply a integer key into the lower level > >> networking subsystem. Re-using once the link it was the key for > >> has been closed makes no sense. You may well get the same integer > >> value if you close a socket then > >> open a new one but its irrelevant. > >> > > > >After a DisconnctEx returns successfully, the socket in question can > >be reused for AcceptEx or ConnectEx. No need to call WSASocket to > >make a new one. > > Seems WSASocket() returns a structure with a whole load of crap in it > unlike posix socket() which returns an int. So maybe in win32 it does > make sense. > WSASocket() return handle, which is pointer-sized. Exactly the same as socket() in that regard. BTW, WSASocket() is a specialised function that is used rather rarely. I had never seen it used. Supposedly, it was more useful back when IP networking was less dominant.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-07-13 13:08 -0700 |
| Message-ID | <1133gjo$3s3f5$2@dont-email.me> |
| In reply to | #124293 |
On 7/12/2026 1:05 PM, Michael S wrote:
> On Sun, 12 Jul 2026 15:19:52 -0000 (UTC)
> boltar@caprica.universe wrote:
>
>> On Sat, 11 Jul 2026 14:11:15 -0700
>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
>>> On 7/11/2026 2:32 AM, boltar@caprica.universe wrote:
>>>> On Fri, 10 Jul 2026 15:36:42 -0700
>>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
>>>>> On 7/10/2026 2:25 AM, boltar@caprica.universe wrote:
>>>>>> On Fri, 10 Jul 2026 00:16:41 -0700
>>>>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
>>>>>>> On 7/5/2026 8:49 AM, boltar@caprica.universe wrote:
>>>>>>>> Why? Once its down a socket - in unix - is just an integer
>>>>>>>> pointing to nothing.
>>>>>>>> What difference does it make if the same value gets reused?
>>>>>>>>
>>>>>>>
>>>>>>> TF_REUSE_SOCKET allows one to reuse a socket in a more
>>>>>>> efficient way. DisconnectEx. Fairly nice! Avoid calling
>>>>>>> WSASocket again.
>>>>>>
>>>>>> Sounds like win32 is a whole other world. Thank god I never had
>>>>>> to both with it.
>>>>>>
>>>>>
>>>>> Fair enough. Reusing a socket is nothing new, right?
>>>>
>>>> On *nix a socket is simply a integer key into the lower level
>>>> networking subsystem. Re-using once the link it was the key for
>>>> has been closed makes no sense. You may well get the same integer
>>>> value if you close a socket then
>>>> open a new one but its irrelevant.
>>>>
>>>
>>> After a DisconnctEx returns successfully, the socket in question can
>>> be reused for AcceptEx or ConnectEx. No need to call WSASocket to
>>> make a new one.
>>
>> Seems WSASocket() returns a structure with a whole load of crap in it
>> unlike posix socket() which returns an int. So maybe in win32 it does
>> make sense.
>>
>
> WSASocket() return handle, which is pointer-sized.
> Exactly the same as socket() in that regard.
>
> BTW, WSASocket() is a specialised function that is used rather rarely.
> I had never seen it used.
> Supposedly, it was more useful back when IP networking was less
> dominant.
WSASocket is more fine grain than socket. Also, its needed for
overlapped io on the windozer:
int
create_accept(
per_socket& listen_sock, // also renamed for
consistency
per_socket& accept_sock, // <--- demon slain
per_io& pio
) {
accept_sock.m_raw.m_socket = WSASocket(
AF_INET, SOCK_STREAM, IPPROTO_TCP,
nullptr, 0, WSA_FLAG_OVERLAPPED
);
if (accept_sock.m_raw.m_socket == INVALID_SOCKET)
{
std::cout << "create_accept WSASocket() failed: "
<< WSAGetLastError() << "\n";
return 1;
}
std::cout << "accept_socket = " <<
accept_sock.m_raw.m_socket << "\n";
pio.m_raw.m_buf = accept_sock.m_raw.m_buf;
pio.m_raw.m_buf_n = accept_sock.m_raw.m_buf_n;
pio.m_raw.m_per_socket = &accept_sock;
pio.m_raw.m_state |= CT_PER_IO_STATE_ACCEPT;
DWORD bytes_received = 0;
BOOL ok = m_winsock.m_wsaex.m_acceptex(
listen_sock.m_raw.m_socket,
accept_sock.m_raw.m_socket,
pio.m_raw.m_buf,
0,
sizeof(SOCKADDR_IN) + 16,
sizeof(SOCKADDR_IN) + 16,
&bytes_received,
&pio.m_raw.m_ol
);
if (!ok && WSAGetLastError() != ERROR_IO_PENDING)
{
std::cout << "AcceptEx failed: " <<
WSAGetLastError() << "\n";
return 1;
}
std::cout << "AcceptEx posted!\n";
return 0;
}
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-07-16 13:56 -0700 |
| Message-ID | <113bghb$29j5c$1@dont-email.me> |
| In reply to | #124298 |
On 7/13/2026 1:08 PM, Chris M. Thomasson wrote:
[...]
> WSASocket is more fine grain than socket. Also, its needed for
> overlapped io on the windozer:
>
> int
> create_accept(
> per_socket& listen_sock, // also renamed for
> consistency
> per_socket& accept_sock, // <--- demon slain
> per_io& pio
> ) {
> accept_sock.m_raw.m_socket = WSASocket(
> AF_INET, SOCK_STREAM, IPPROTO_TCP,
> nullptr, 0, WSA_FLAG_OVERLAPPED
> );
This is where I need to prime my per_socket pools with sockets! Instead
of calling WSASocket here, create_accept can check a pool of them first.
If that is empty, then we can create another one and handle the errors
if that fails.
>
> if (accept_sock.m_raw.m_socket == INVALID_SOCKET)
> {
> std::cout << "create_accept WSASocket() failed: "
> << WSAGetLastError() << "\n";
> return 1;
> }
>
> std::cout << "accept_socket = " <<
> accept_sock.m_raw.m_socket << "\n";
>
> pio.m_raw.m_buf = accept_sock.m_raw.m_buf;
> pio.m_raw.m_buf_n = accept_sock.m_raw.m_buf_n;
>
> pio.m_raw.m_per_socket = &accept_sock;
> pio.m_raw.m_state |= CT_PER_IO_STATE_ACCEPT;
>
> DWORD bytes_received = 0;
>
> BOOL ok = m_winsock.m_wsaex.m_acceptex(
> listen_sock.m_raw.m_socket,
> accept_sock.m_raw.m_socket,
> pio.m_raw.m_buf,
> 0,
> sizeof(SOCKADDR_IN) + 16,
> sizeof(SOCKADDR_IN) + 16,
> &bytes_received,
> &pio.m_raw.m_ol
> );
>
> if (!ok && WSAGetLastError() != ERROR_IO_PENDING)
> {
> std::cout << "AcceptEx failed: " <<
> WSAGetLastError() << "\n";
> return 1;
> }
>
> std::cout << "AcceptEx posted!\n";
> return 0;
> }
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-07-16 13:58 -0700 |
| Message-ID | <113bgmg$29j5c$2@dont-email.me> |
| In reply to | #124314 |
On 7/16/2026 1:56 PM, Chris M. Thomasson wrote:
> On 7/13/2026 1:08 PM, Chris M. Thomasson wrote:
> [...]
>> WSASocket is more fine grain than socket. Also, its needed for
>> overlapped io on the windozer:
>>
>> int
>> create_accept(
>> per_socket& listen_sock, // also renamed for
>> consistency
>> per_socket& accept_sock, // <--- demon slain
>> per_io& pio
>> ) {
>> accept_sock.m_raw.m_socket = WSASocket(
>> AF_INET, SOCK_STREAM, IPPROTO_TCP,
>> nullptr, 0, WSA_FLAG_OVERLAPPED
>> );
>
> This is where I need to prime my per_socket pools with sockets! Instead
> of calling WSASocket here, create_accept can check a pool of them first.
> If that is empty, then we can create another one and handle the errors
> if that fails.
Well, that should be before create_accept anyway. accept_sock should
already have a working accept_sock.m_raw.m_socket
>
>
>
>>
>> if (accept_sock.m_raw.m_socket == INVALID_SOCKET)
>> {
>> std::cout << "create_accept WSASocket()
>> failed: "
>> << WSAGetLastError() << "\n";
>> return 1;
>> }
>>
>> std::cout << "accept_socket = " <<
>> accept_sock.m_raw.m_socket << "\n";
>>
>> pio.m_raw.m_buf = accept_sock.m_raw.m_buf;
>> pio.m_raw.m_buf_n = accept_sock.m_raw.m_buf_n;
>>
>> pio.m_raw.m_per_socket = &accept_sock;
>> pio.m_raw.m_state |= CT_PER_IO_STATE_ACCEPT;
>>
>> DWORD bytes_received = 0;
>>
>> BOOL ok = m_winsock.m_wsaex.m_acceptex(
>> listen_sock.m_raw.m_socket,
>> accept_sock.m_raw.m_socket,
>> pio.m_raw.m_buf,
>> 0,
>> sizeof(SOCKADDR_IN) + 16,
>> sizeof(SOCKADDR_IN) + 16,
>> &bytes_received,
>> &pio.m_raw.m_ol
>> );
>>
>> if (!ok && WSAGetLastError() != ERROR_IO_PENDING)
>> {
>> std::cout << "AcceptEx failed: " <<
>> WSAGetLastError() << "\n";
>> return 1;
>> }
>>
>> std::cout << "AcceptEx posted!\n";
>> return 0;
>> }
>
[toc] | [prev] | [next] | [standalone]
| From | Ross Finlayson <ross.a.finlayson@gmail.com> |
|---|---|
| Date | 2026-07-03 10:45 -0700 |
| Message-ID | <QLKcnZQ5i7bFaNr3nZ2dnZfqnPGdnZ2d@giganews.com> |
| In reply to | #124171 |
On 07/02/2026 11:41 AM, Chris M. Thomasson wrote: > On 7/2/2026 1:13 AM, boltar@caprica.universe wrote: >> On Wed, 1 Jul 2026 12:23:45 -0700 >> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>> On 6/30/2026 3:44 AM, boltar@caprica.universe wrote: >>>> On Tue, 30 Jun 2026 01:42:37 -0700 >>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled: >>>>> On 6/30/2026 1:27 AM, Wuns Haerst wrote: >>>>>> I measured the time it takes to create a thread on both Windows and >>>>>> Linux. On Windows, it takes around 120,000 clock cycles, whereas on >>>>>> Linux, it takes about a third of that. >>>>>> It occurred to me that one could simply inline the thread's main >>>>>> function. This would eliminate the need for the operating system >>>>>> call to create the thread. In this scenario, the compiler — or its >>>>>> runtime — would have to handle the scheduling. >>>>>> I estimate that this would reduce the thread creation overhead to >>>>>> just a few clock cycles, making thread pools unnecessary. I’m just >>>>>> not sure yet exactly how to go about implementing this. Perhaps >>>>>> someone here can help me with it. >>>>>> Please send any relevant suggestions via email only, as I intend >>>>>> to patent this idea once it is fully developed. >>>>> >>>>> Well, we should never be creating threads all the time and joining >>>>> them, ect. Just make a nice thread pool up front. Adding more >>>>> threads to it should be fairly rare. >>>> >>>> "Just make a threadpool" is a non trivial coding task and completely >>>> unnecessary for programs that only create threads ad hoc now and >>>> then. If >>>> you're writing a high throughput server then sure, otherwise no. >>>> >>> >>> Thread pools are not all that hard. Since you are using threads anyway, >> >> They're hard enough to make it a lot of pointless work if its not >> necessary. As I said, if you're creating threads every few >> milliseconds then >> use a thread pool. If you're just creating a thread every few seconds >> or longer then a pool is a complete waste of time. > > Thread per connection model? If that works for your work load, so be it. > Just don't be alarmed if you get 10000 threads all of sudden. Or, say a > connection comes in every second for say a half an hour. 1800 > connections? Also you need to think about a connection that sends a > little data then just sits there doing nothing for say 20 minutes. > > >>> how are you handling the sync in your program logic to them? What do >>> they do? >> >> Is that supposed to be some kind of trick question? > > No. It means how to you say, join them, or are you detaching them? How > can you gain data from them? You need to know all about this if you are > going to use threads at all. Well, imvho that is... > > Do you have a "reaper" thread that can conduct "maintenance"? Zombie > states? Are you do graceful shutdowns? "Sweeper" usually it's called, here, for the case of timeouts. Have you heard of re-routines? It's a model of co-operative multi-threading with async everywhere yet written in the language as procedural flow of control with exceptions, thusly "async" nowhere. Have you heard of re-routines? ....
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-07-03 12:36 -0700 |
| Message-ID | <11292v6$3l0da$1@dont-email.me> |
| In reply to | #124175 |
On 7/3/2026 10:45 AM, Ross Finlayson wrote:
> On 07/02/2026 11:41 AM, Chris M. Thomasson wrote:
>> On 7/2/2026 1:13 AM, boltar@caprica.universe wrote:
>>> On Wed, 1 Jul 2026 12:23:45 -0700
>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
>>>> On 6/30/2026 3:44 AM, boltar@caprica.universe wrote:
>>>>> On Tue, 30 Jun 2026 01:42:37 -0700
>>>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
>>>>>> On 6/30/2026 1:27 AM, Wuns Haerst wrote:
>>>>>>> I measured the time it takes to create a thread on both Windows and
>>>>>>> Linux. On Windows, it takes around 120,000 clock cycles, whereas on
>>>>>>> Linux, it takes about a third of that.
>>>>>>> It occurred to me that one could simply inline the thread's main
>>>>>>> function. This would eliminate the need for the operating system
>>>>>>> call to create the thread. In this scenario, the compiler — or its
>>>>>>> runtime — would have to handle the scheduling.
>>>>>>> I estimate that this would reduce the thread creation overhead to
>>>>>>> just a few clock cycles, making thread pools unnecessary. I’m just
>>>>>>> not sure yet exactly how to go about implementing this. Perhaps
>>>>>>> someone here can help me with it.
>>>>>>> Please send any relevant suggestions via email only, as I intend
>>>>>>> to patent this idea once it is fully developed.
>>>>>>
>>>>>> Well, we should never be creating threads all the time and joining
>>>>>> them, ect. Just make a nice thread pool up front. Adding more
>>>>>> threads to it should be fairly rare.
>>>>>
>>>>> "Just make a threadpool" is a non trivial coding task and completely
>>>>> unnecessary for programs that only create threads ad hoc now and
>>>>> then. If
>>>>> you're writing a high throughput server then sure, otherwise no.
>>>>>
>>>>
>>>> Thread pools are not all that hard. Since you are using threads anyway,
>>>
>>> They're hard enough to make it a lot of pointless work if its not
>>> necessary. As I said, if you're creating threads every few
>>> milliseconds then
>>> use a thread pool. If you're just creating a thread every few seconds
>>> or longer then a pool is a complete waste of time.
>>
>> Thread per connection model? If that works for your work load, so be it.
>> Just don't be alarmed if you get 10000 threads all of sudden. Or, say a
>> connection comes in every second for say a half an hour. 1800
>> connections? Also you need to think about a connection that sends a
>> little data then just sits there doing nothing for say 20 minutes.
>>
>>
>>>> how are you handling the sync in your program logic to them? What do
>>>> they do?
>>>
>>> Is that supposed to be some kind of trick question?
>>
>> No. It means how to you say, join them, or are you detaching them? How
>> can you gain data from them? You need to know all about this if you are
>> going to use threads at all. Well, imvho that is...
>>
>> Do you have a "reaper" thread that can conduct "maintenance"? Zombie
>> states? Are you do graceful shutdowns?
>
> "Sweeper" usually it's called, here, for the case of timeouts.
Timeouts, general maintenance, etc. Fwiw, it can be a single function
that can be run on any thread. Say to gain entry:
if (try_lock())
{
// reaper logic
unlock();
}
that way any thread can act like a reaper, but its "best" to keep that
in a dedicated thread. Also, it ensures that only one reaper is alive at
any one time and its non-blocking via try_lock. Its just an easy way to
do it.
Reaper logic never blocks.
> Have you heard of re-routines? It's a model of co-operative
> multi-threading with async everywhere yet written in the language as
> procedural flow of control with exceptions, thusly "async" nowhere.
>
> Have you heard of re-routines? ....
Building on top of coroutines, with a stack? Like Fibers? I have used
continuations before. But, re-routines? Humm... Not ringing a bell.
Fwiw, here is a fun paper I read many moons ago, iirc back in 2002:
https://www.microsoft.com/en-us/research/publication/using-cohort-scheduling-to-enhance-server-performance/?msockid=156c5513e5e96cdb283d4228e46a6db8
https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/tr-2001-39.pdf
This was way back when I was working with winnt 4.0.
[toc] | [prev] | [next] | [standalone]
| From | Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> |
|---|---|
| Date | 2026-07-28 12:50 +0100 |
| Message-ID | <114a52b$1ms$2@dont-email.me> |
| In reply to | #124169 |
On 02/07/2026 09:13, boltar@caprica.universe wrote: > [thread pools are] > hard enough to make it a lot of pointless work if its not > necessary. It's so not hard in C++. Additionally, you can just use a public-domain library, which, on the old, real, internet were findable a dime a dozen - less than a dime a dozen. > As I said, if you're creating threads every few milliseconds > then > use a thread pool. If you're just creating a thread every few seconds or > longer then a pool is a complete waste of time. Unless it's part of a heavy interactive sequence and you need each part to be rapid so you shave time of each bit of it. I thought this was all standard knowledge and had been since the 1980s when threads started to be created as heavy-weight tasks instead of being made as light-weight CoEs then converted to heavy-weight ones at an opportune moment as they had commonly been up to the 1980s? -- Tristan Wibberley The message body is Copyright (C) 2026 Tristan Wibberley except citations and quotations noted. All Rights Reserved except that you may, of course, cite it academically giving credit to me, distribute it verbatim as part of a usenet system or its archives, and use it to promote my greatness and general superiority without misrepresentation of my opinions other than my opinion of my greatness and general superiority which you _may_ misrepresent. You definitely MAY NOT train any production AI system with it but you may train experimental AI that will only be used for evaluation of the AI methods it implements.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2026-06-30 11:07 +0200 |
| Message-ID | <112010o$uptn$1@dont-email.me> |
| In reply to | #124149 |
On 30/06/2026 10:27, Wuns Haerst wrote: > I measured the time it takes to create a thread on both Windows and > Linux. On Windows, it takes around 120,000 clock cycles, whereas on > Linux, it takes about a third of that. > It occurred to me that one could simply inline the thread's main > function. This would eliminate the need for the operating system > call to create the thread. In this scenario, the compiler — or its > runtime — would have to handle the scheduling. > I estimate that this would reduce the thread creation overhead to > just a few clock cycles, making thread pools unnecessary. I’m just > not sure yet exactly how to go about implementing this. Perhaps > someone here can help me with it. > Please send any relevant suggestions via email only, as I intend > to patent this idea once it is fully developed. It sounds like you have little experience or understanding of multi-threading or multi-tasking, what "inlining" means, and what compilers and runtimes can do. For general threads or tasks on a general-purpose OS, what you are asking is not possible. People have got patents on impossible things before - plenty have been granted for perpetual motion machines - but it's a waste of time and effort. If you think you have had a brilliant idea to make multi-threading vastly more efficient, and no one else has thought of this before, you are delusional. It is entirely possible to have coroutines, lightweight threads, fibres, goroutines, protothreads, etc., that all run within the same OS thread but allow a certain amount of disconnection of execution. Generally speaking, the more flexibility and independence you have in the execution of these types of thread, the greater the overhead in creating them. If they are actually going to run simultaneously on a multi-core system, you will be using OS threads somewhere. The lowest overhead existing solution, to my knowledge, is "protothreads". C++ has standardised support for coroutines, though it is a bit clunky as a late addition to the language. Go has goroutines that are fundamental to the language, and thus better integrated.
[toc] | [prev] | [next] | [standalone]
Page 8 of 10 — ← Prev page 1 … 6 7 [8] 9 10 Next page →
Back to top | Article view | comp.lang.c++
csiph-web