Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #117659 > unrolled thread
| Started by | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| First post | 2023-11-08 15:56 +0100 |
| Last post | 2023-11-13 22:46 -0800 |
| Articles | 20 on this page of 259 — 9 participants |
Back to article view | Back to comp.lang.c++
A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-08 15:56 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-08 19:31 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-08 20:56 +0100
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-08 23:25 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 05:33 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 20:36 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 05:38 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 20:42 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:08 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:11 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:12 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:17 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:35 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:39 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:40 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:41 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:42 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:44 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:44 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:45 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:48 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:50 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:58 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 22:46 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:52 +0100
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-14 21:10 -0500
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-15 06:07 +0100
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-17 21:16 -0500
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-18 04:06 +0100
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-18 12:53 -0500
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-18 20:04 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-18 19:24 +0000
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-18 20:29 +0000
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-18 21:46 +0000
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-18 20:18 -0500
Re: A Java- / .NET-like monitor Michael S <already5chosen@yahoo.com> - 2023-11-24 01:14 +0200
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-23 21:35 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-24 08:59 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-24 01:17 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-24 10:25 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-24 15:59 +0000
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-24 18:33 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-24 15:39 -0800
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-25 00:08 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-24 16:27 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-25 14:47 -0800
Re: A Java- / .NET-like monitor "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2023-11-25 13:02 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-25 17:28 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-25 18:48 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-25 18:09 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-25 13:12 +0100
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-25 18:10 +0000
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-25 19:30 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-25 14:57 -0800
Re: A Java- / .NET-like monitor Michael S <already5chosen@yahoo.com> - 2023-11-26 01:29 +0200
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-25 15:56 -0800
Re: A Java- / .NET-like monitor David Brown <david.brown@hesbynett.no> - 2023-11-26 13:54 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-26 14:38 +0100
Re: A Java- / .NET-like monitor David Brown <david.brown@hesbynett.no> - 2023-11-26 16:28 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-26 18:51 +0100
Re: A Java- / .NET-like monitor David Brown <david.brown@hesbynett.no> - 2023-11-26 20:27 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-26 14:38 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-26 15:00 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-27 05:23 +0100
Re: A Java- / .NET-like monitor David Brown <david.brown@hesbynett.no> - 2023-11-27 10:38 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-27 10:55 +0100
Re: A Java- / .NET-like monitor David Brown <david.brown@hesbynett.no> - 2023-11-27 11:19 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-27 12:32 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-26 22:55 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-27 15:15 -0800
Re: A Java- / .NET-like monitor David Brown <david.brown@hesbynett.no> - 2023-11-28 09:03 +0100
Re: A Java- / .NET-like monitor David Brown <david.brown@hesbynett.no> - 2023-11-25 13:58 +0100
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-18 20:09 -0500
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-19 05:58 +0100
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-19 05:02 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-19 07:00 +0100
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-19 06:08 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-19 12:05 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-19 12:08 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-19 12:11 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-19 12:17 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-20 13:26 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-20 12:18 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-21 10:25 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-23 21:38 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-24 08:56 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-24 01:22 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-24 19:10 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-24 15:43 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-25 13:04 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-25 15:06 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-26 11:35 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-26 15:45 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-27 05:24 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-26 22:22 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-27 08:57 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-27 00:28 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-27 09:34 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-27 14:59 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-27 14:59 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-27 15:19 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-28 15:13 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-18 12:46 -0800
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-18 21:47 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-18 14:02 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-18 20:20 -0500
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-20 13:12 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 08:01 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 08:01 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:50 +0100
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-11 17:45 -0500
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-12 05:43 +0100
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-12 05:02 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-12 11:00 +0100
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-12 17:18 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-13 07:33 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-13 07:47 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 12:50 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 06:20 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 21:21 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 07:44 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 22:51 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 22:55 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 08:00 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 08:07 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 23:08 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 23:07 -0800
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-14 15:18 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 16:46 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-14 16:09 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 17:41 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 18:41 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-14 12:25 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-14 14:25 -0800
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-14 22:50 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-15 12:07 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-15 05:57 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-15 12:08 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-16 03:59 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-16 15:02 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-16 18:12 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-16 17:45 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-27 15:24 -0800
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-12 17:53 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-12 12:51 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-12 19:33 -0500
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-13 04:50 +0000
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-13 22:05 -0500
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-14 03:30 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 22:35 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-14 20:26 -0500
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-15 12:11 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-15 23:07 -0500
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-16 06:39 +0000
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-16 21:48 -0500
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-17 16:29 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-17 10:22 -0800
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-17 18:37 +0000
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-18 00:45 +0000
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-18 02:30 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-16 11:11 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-13 07:35 +0100
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-13 15:05 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-13 16:36 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-13 17:24 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-12 12:48 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-12 19:29 -0500
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-12 16:44 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-16 14:16 -0800
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-13 04:48 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 14:32 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-13 21:27 -0500
Re: A Java- / .NET-like monitor scott@slp53.sl.home (Scott Lurndal) - 2023-11-14 15:12 +0000
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-14 20:35 -0500
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-13 21:58 -0500
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-14 03:27 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 21:28 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 21:29 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-14 20:47 -0500
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-15 12:18 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-15 12:20 -0800
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-15 21:26 +0000
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-16 00:25 -0500
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-14 20:42 -0500
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-28 15:32 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-12 19:17 -0500
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-09 05:17 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:18 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:20 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:19 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:20 -0800
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-08 23:51 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:10 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 15:32 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 05:35 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:17 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:22 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:27 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:29 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:31 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:34 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:36 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 06:40 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:42 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 07:32 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 22:54 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 23:01 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 23:03 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:30 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 21:32 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 14:59 -0800
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-08 19:49 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-08 18:16 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 13:49 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 05:37 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 20:40 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 20:39 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 13:41 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 05:36 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-08 20:41 -0800
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-08 18:16 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 10:07 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-09 01:11 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-09 10:17 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-09 01:22 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-09 01:23 -0800
Re: A Java- / .NET-like monitor Branimir Maksimovic <branimir.maksimovic@icloud.com> - 2023-11-10 13:56 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-10 15:08 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-10 15:15 +0100
Re: A Java- / .NET-like monitor Branimir Maksimovic <branimir.maksimovic@icloud.com> - 2023-11-11 02:59 +0000
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-10 12:44 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-11 04:53 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-10 20:09 -0800
Re: A Java- / .NET-like monitor Branimir Maksimovic <branimir.maksimovic@icloud.com> - 2023-11-11 04:25 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-11 07:07 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-11 11:41 +0100
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-11 16:39 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-11 11:42 -0800
Re: A Java- / .NET-like monitor Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-11-11 17:49 -0500
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-12 05:40 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-12 12:46 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 23:13 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 10:04 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-14 01:21 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 11:00 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-14 02:08 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-14 11:23 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-14 12:27 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-14 12:29 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-15 05:54 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-15 12:21 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-16 04:00 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-15 19:10 -0800
Re: A Java- / .NET-like monitor Kaz Kylheku <864-117-4973@kylheku.com> - 2023-11-16 03:21 +0000
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-16 06:36 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-16 13:06 -0800
Re: A Java- / .NET-like monitor Bonita Montero <Bonita.Montero@gmail.com> - 2023-11-17 06:57 +0100
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-11 11:41 -0800
Re: A Java- / .NET-like monitor "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-13 22:46 -0800
Page 11 of 13 — ← Prev page 1 … 9 10 [11] 12 13 Next page →
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2023-11-09 06:34 +0100 |
| Message-ID | <uihr10$22fdu$1@raubtier-asyl.eternal-september.org> |
| In reply to | #117707 |
Am 09.11.2023 um 06:31 schrieb Chris M. Thomasson: > Yup. Porting your code to Relacy is going to force me to read every damn > line of your code. So, touche? Reading the code doesn't hurt since the functions are short.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 21:36 -0800 |
| Message-ID | <uihr5j$228mv$12@dont-email.me> |
| In reply to | #117709 |
On 11/8/2023 9:34 PM, Bonita Montero wrote: > Am 09.11.2023 um 06:31 schrieb Chris M. Thomasson: > >> Yup. Porting your code to Relacy is going to force me to read every >> damn line of your code. So, touche? > > Reading the code doesn't hurt since the functions are short. > Porting your code to Relacy makes me read every damn line. You masking is interesting.
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2023-11-09 06:40 +0100 |
| Message-ID | <uihrd3$22gqs$2@raubtier-asyl.eternal-september.org> |
| In reply to | #117711 |
Am 09.11.2023 um 06:36 schrieb Chris M. Thomasson: > Porting your code to Relacy makes me read every damn line. > You masking is interesting. My code is understandable if you know MT-primitives and SysV-IPC. There's nothing "damn" with my code.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 21:42 -0800 |
| Message-ID | <uihrfi$228mv$15@dont-email.me> |
| In reply to | #117713 |
On 11/8/2023 9:40 PM, Bonita Montero wrote: > Am 09.11.2023 um 06:36 schrieb Chris M. Thomasson: > >> Porting your code to Relacy makes me read every damn line. >> You masking is interesting. > > My code is understandable if you know MT-primitives > and SysV-IPC. There's nothing "damn" with my code. Oh well, like I said, you seem to be a fun person to work with...
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2023-11-09 07:32 +0100 |
| Message-ID | <uihudf$230h4$1@raubtier-asyl.eternal-september.org> |
| In reply to | #117716 |
Am 09.11.2023 um 06:42 schrieb Chris M. Thomasson: > On 11/8/2023 9:40 PM, Bonita Montero wrote: >> My code is understandable if you know MT-primitives >> and SysV-IPC. There's nothing "damn" with my code. > Oh well, like I said, you seem to be a fun person to work with... If you were here we would go through the code together and you would immediately understand it.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 22:54 -0800 |
| Message-ID | <uihvmj$2351m$2@dont-email.me> |
| In reply to | #117726 |
On 11/8/2023 10:32 PM, Bonita Montero wrote: > Am 09.11.2023 um 06:42 schrieb Chris M. Thomasson: > >> On 11/8/2023 9:40 PM, Bonita Montero wrote: > >>> My code is understandable if you know MT-primitives >>> and SysV-IPC. There's nothing "damn" with my code. > >> Oh well, like I said, you seem to be a fun person to work with... > > If you were here we would go through the code together > and you would immediately understand it. > Since I have to model one of my experimental algorithms in Relacy anyway, well, I will be right up in it. Wrt my code, well, its trying to make some fractals go volumetric and I need to highly efficient and specialized LIFO/FIFO stack/queue system for it. They are running on the CPU, I might even be able to get it run in shaders, but for now, I need to work on modeling my sketch of my code in Relacy, create some test units, and give it a go. Fwiw, here is one of my vector fields: https://youtu.be/poXeq5V0dso This used an older queue of mine to help distribute the field processing across multiple processors.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 23:01 -0800 |
| Message-ID | <uii03m$2351m$3@dont-email.me> |
| In reply to | #117728 |
On 11/8/2023 10:54 PM, Chris M. Thomasson wrote: > On 11/8/2023 10:32 PM, Bonita Montero wrote: >> Am 09.11.2023 um 06:42 schrieb Chris M. Thomasson: >> >>> On 11/8/2023 9:40 PM, Bonita Montero wrote: >> >>>> My code is understandable if you know MT-primitives >>>> and SysV-IPC. There's nothing "damn" with my code. >> >>> Oh well, like I said, you seem to be a fun person to work with... >> >> If you were here we would go through the code together >> and you would immediately understand it. >> > > Since I have to model one of my experimental algorithms in Relacy > anyway, well, I will be right up in it. Wrt my code, well, its trying to > make some fractals go volumetric and I need to highly efficient and > specialized LIFO/FIFO stack/queue system for it. They are running on the > CPU, I might even be able to get it run in shaders, but for now, I need > to work on modeling my sketch of my code in Relacy, create some test > units, and give it a go. Fwiw, here is one of my vector fields: > > https://youtu.be/poXeq5V0dso > > This used an older queue of mine to help distribute the field processing > across multiple processors. Fwiw, this one is basically embarrassingly parallel to create each frame. Well, that is kind of cheating wrt embarrassingly parallel, but, oh well: https://youtu.be/DrPp6xfLe4Q This one is from a recursive algorithm of mine, not too efficient wrt the generation part that gives me my field points to work with. It takes a while to render an animation in 4k. The recursive nature of it can blow a threads stack if I get too detailed. So, I need to refine my current quick and dirty proof of concept code, so to speak. It is kind of embarrassingly parallel...
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 23:03 -0800 |
| Message-ID | <uii07j$2351m$4@dont-email.me> |
| In reply to | #117729 |
On 11/8/2023 11:01 PM, Chris M. Thomasson wrote: > On 11/8/2023 10:54 PM, Chris M. Thomasson wrote: >> On 11/8/2023 10:32 PM, Bonita Montero wrote: >>> Am 09.11.2023 um 06:42 schrieb Chris M. Thomasson: >>> >>>> On 11/8/2023 9:40 PM, Bonita Montero wrote: >>> >>>>> My code is understandable if you know MT-primitives >>>>> and SysV-IPC. There's nothing "damn" with my code. >>> >>>> Oh well, like I said, you seem to be a fun person to work with... >>> >>> If you were here we would go through the code together >>> and you would immediately understand it. >>> >> >> Since I have to model one of my experimental algorithms in Relacy >> anyway, well, I will be right up in it. Wrt my code, well, its trying >> to make some fractals go volumetric and I need to highly efficient and >> specialized LIFO/FIFO stack/queue system for it. They are running on >> the CPU, I might even be able to get it run in shaders, but for now, I >> need to work on modeling my sketch of my code in Relacy, create some >> test units, and give it a go. Fwiw, here is one of my vector fields: >> >> https://youtu.be/poXeq5V0dso >> >> This used an older queue of mine to help distribute the field >> processing across multiple processors. > > Fwiw, this one is basically embarrassingly parallel to create each > frame. Well, that is kind of cheating wrt embarrassingly parallel, but, > oh well: > > https://youtu.be/DrPp6xfLe4Q > > This one is from a recursive algorithm of mine, not too efficient wrt > the generation part that gives me my field points to work with. It takes > a while to render an animation in 4k. The recursive nature of it can > blow a threads stack if I get too detailed. So, I need to refine my > current quick and dirty proof of concept code, so to speak. It is kind > of embarrassingly parallel... oh shit, I forgot the damn link: https://youtu.be/YsAkm0VlCsw (should be 4k, damn it!) Also, this one is ripe for for improvement. I just know that my new queue system is going to work for it wrt generating its frames. https://youtu.be/HwIkk9zENcg Will create another thread to continue this.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 21:30 -0800 |
| Message-ID | <uihqpl$228mv$8@dont-email.me> |
| In reply to | #117704 |
On 11/8/2023 9:27 PM, Chris M. Thomasson wrote: > On 11/8/2023 9:22 PM, Bonita Montero wrote: >> Am 09.11.2023 um 06:17 schrieb Chris M. Thomasson: >> >>> Humm... Sounds good. However, I need to try it out. Also, if you >>> don't mind I might actually model it in relacy. >> >> I've witten my own unit test. The Win32 code worked immediately, >> but the SysV-code didn't work immediately also because I forgot >> to have IPC_NOWAIT while releasing a semaphore. Why is there a >> way to wait for the release of a mutex to be accepted by another >> thread ? Who comes up with that ? > > Well, invvvho, it might be prudent of me to model it in Relacy. The act > of me porting your work over into its logic base is going to get me > really intimate with your code. Can you feel me? lol. ;^) I have to work on some of my fractal IFS right now, but, I will try to port your work over to Relacy. Fwiw, here is a taste of some work I ave to do right now: https://paulbourke.net/fractals/multijulia I am trying to create a nice volumetric form of it.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 21:32 -0800 |
| Message-ID | <uihqto$228mv$10@dont-email.me> |
| In reply to | #117706 |
On 11/8/2023 9:30 PM, Chris M. Thomasson wrote: > On 11/8/2023 9:27 PM, Chris M. Thomasson wrote: >> On 11/8/2023 9:22 PM, Bonita Montero wrote: >>> Am 09.11.2023 um 06:17 schrieb Chris M. Thomasson: >>> >>>> Humm... Sounds good. However, I need to try it out. Also, if you >>>> don't mind I might actually model it in relacy. >>> >>> I've witten my own unit test. The Win32 code worked immediately, >>> but the SysV-code didn't work immediately also because I forgot >>> to have IPC_NOWAIT while releasing a semaphore. Why is there a >>> way to wait for the release of a mutex to be accepted by another >>> thread ? Who comes up with that ? >> >> Well, invvvho, it might be prudent of me to model it in Relacy. The >> act of me porting your work over into its logic base is going to get >> me really intimate with your code. > > Can you feel me? lol. ;^) > > I have to work on some of my fractal IFS right now, but, I will try to > port your work over to Relacy. Fwiw, here is a taste of some work I ave > to do right now: > > https://paulbourke.net/fractals/multijulia > > I am trying to create a nice volumetric form of it. https://youtu.be/XpbPzrSXOgk
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 14:59 -0800 |
| Message-ID | <uih3s2$1r33v$1@dont-email.me> |
| In reply to | #117663 |
On 11/8/2023 11:56 AM, Bonita Montero wrote: > Am 08.11.2023 um 20:49 schrieb Kaz Kylheku: > >> No, the "monitor" idea you're proposing is different in this >> way. > > That's not true. That spurious wakesups may happen with a mutex and > a condition variable are constituted in that both are separate enti- > ties. Spuriuos wakesups never happen with my implementation, but > stolen wakeups are still possible. > >> Monitors as they are understood in computer science (first described by >> C. A. R. Hoare) do not combine the monitor and condition variables into >> one object; they are distinct entities: one monitor, zero to many >> conditions. > > The way monitors work does not suggest an implementation, or they can > be based internally on a mutex and a condition variable, but if you > have a monitor that never has spurious wakeups, it is implemented > like mine. > >> To avoid muddying the debate with nonstandard terminology, you might >> want to call your cockamamie idea "bonitor". > > I've implemented a monitor without spurious wakeups. > Yawn.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <864-117-4973@kylheku.com> |
|---|---|
| Date | 2023-11-08 19:49 +0000 |
| Message-ID | <20231108114723.256@kylheku.com> |
| In reply to | #117660 |
On 2023-11-08, Bonita Montero <Bonita.Montero@gmail.com> wrote: > Am 08.11.2023 um 19:16 schrieb Kaz Kylheku: > >> POSIX-style mutexes and condition variables are actually Mesa-style >> monitors. > > A monitor is different because the mutex and condition variable > is joined in a monitor which allows the shown optimization while > waiting to be notified. No, the "monitor" idea you're proposing is different in this way. Monitors as they are understood in computer science (first described by C. A. R. Hoare) do not combine the monitor and condition variables into one object; they are distinct entities: one monitor, zero to many conditions. To avoid muddying the debate with nonstandard terminology, you might want to call your cockamamie idea "bonitor". -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca NOTE: If you use Google Groups, I don't see you, unless you're whitelisted.
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2023-11-08 18:16 +0100 |
| Message-ID | <uigfpu$1mmp3$1@raubtier-asyl.eternal-september.org> |
| In reply to | #117659 |
Am 08.11.2023 um 15:56 schrieb Bonita Montero:
> Java and .NET have monitor objects instead of a combination of mutexes
> and condition variables. The advantage of a monitor object is that when
> you wait for a monitor to be signalled you can wait for that and for the
> mutexe's semaphore to be unlocked in _one_ step. With a condition varia-
> ble you have first to wait for the notify()-semaphore to be signalled
> and for the mutexe's lock in two steps.
> The below code simply has a 32 or 64 bit atomic (depening on if the 64
> bit variant is lock-free or not) and the lower half is the number of
> threads waiting to enter the mutex part and the upper half is the num-
> ber of threads waiting to be notified. As all threads wanting to be
> notified are also waiting for the mutex the lower half is always >=
> the upper half, which I check for in several asserts.
> On Windows waiting to be notified and waiting to lock the mutex part
> to be unlocked is done by WaitForMultipleObjects(). On Linux there's
> no way to wait for mutliple kernel handles to be signalled, but there
> are SystemV semaphore sets which may consist of several semaphores and
> you may have multiple operations to proceed atomically on this set.
> The drawback of combining the mutex and condition-variable parts is
> that you can't have multiple conditions associated with the same mutex.
>
>
> // monitor.h
>
> #pragma once
> #if defined(_WIN32)
> #define NOMINMAX
> #include <Windows.h>
> #elif defined(__unix__)
> #include <sys/types.h>
> #include <sys/sem.h>
> #include <sys/stat.h>
> #else
> #error unsupported platform
> #endif
> #include <atomic>
> #include <semaphore>
> #include <type_traits>
> #if defined(_WIN32)
> #include "xhandle.h"
> #endif
>
> struct monitor
> {
> monitor();
> ~monitor();
> void lock();
> void unlock();
> void wait();
> void notify();
> void notify_all();
> private:
> inline static thread_local char t_dummy;
> static constexpr bool USE64 =
> std::atomic_int64_t::is_always_lock_free;
> using atomic_word_t = std::conditional_t<USE64, uint64_t, uint32_t>;
> static constexpr unsigned BITS = USE64 ? 32 : 16;
> static constexpr atomic_word_t
> ENTER_VALUE = 1,
> SIGNAL_VALUE = USE64 ? 1ull << 32 : 1,
> ENTER_MASK = USE64 ? (uint32_t)-1 : (uint16_t)-1,
> SIGNAL_MASK = USE64 ? (uint64_t)(uint32_t)-1 << 32 :
> (uint32_t)(uint16_t)-1 << 16;
> std::atomic<atomic_word_t> m_atomic;
> std::atomic<char *> m_threadId;
> std::atomic_uint32_t m_recCount;
> #if defined(_WIN32)
> static constexpr uint32_t SEM_MAX = std::numeric_limits<LONG>::max();
> XHANDLE
> m_xhEnterEvt,
> m_xhSignalSem;
> #elif defined(__unix__)
> static constexpr uint32_t SEM_MAX = std::numeric_limits<short>::max();
> int m_sems;
> int semop( std::initializer_list<sembuf> sems );
> #endif
> };
>
> // monitor.cpp
>
> #include <iostream>
> #include <limits>
> #include <system_error>
> #include <cassert>
> #include "monitor.h"
>
> using namespace std;
>
> monitor::monitor() :
> m_atomic( 0 ),
> m_threadId( nullptr )
> #if defined(_WIN32)
> , m_xhEnterEvt( CreateEventA( nullptr, FALSE, FALSE, nullptr ) ),
> m_xhSignalSem( CreateSemaphoreA( nullptr, 0, SEM_MAX, nullptr ) )
> #elif defined(__unix__)
> , m_sems( semget( IPC_PRIVATE, 2, S_IRUSR | S_IWUSR ) )
> #endif
> {
> #if defined(_WIN32)
> if( !m_xhEnterEvt.get() || !m_xhSignalSem.get() )
> throw system_error( GetLastError(), system_category(), "can't
> initialize monitor object" );
> #elif defined(__unix__)
> union semun { int val; void *p; } su;
> su.val = 0;
> #if defined(__linux__)
> if( m_sems == -1 )
> #else
> if( m_sems == -1 || semctl( m_sems, 0, SETVAL, su ) == -1 ||
> semctl( m_sems, 1, SETVAL, su ) == -1 )
> #endif
> throw system_error( errno, system_category(), "can't initialize
> monitor object" );
> #endif
> }
>
> monitor::~monitor()
> {
> #if defined(__unix__)
> int ret = semctl( m_sems, 0, IPC_RMID );
> assert(ret != -1);
> #endif
> }
>
> void monitor::lock()
> {
> if( m_threadId.load( memory_order_relaxed ) == &t_dummy )
> {
> uint32_t oldRecCount = m_recCount.load( memory_order_relaxed );
> if( oldRecCount == (uint32_t)-1 )
> throw system_error( (int)errc::result_out_of_range,
> generic_category(), "montor's recursion count saturated" );
> m_recCount.store( oldRecCount + 1, memory_order_relaxed );
> return;
> }
> atomic_word_t ref = m_atomic.load( memory_order_relaxed );
> do
> {
> if( (ref & ENTER_MASK) == ENTER_MASK )
> throw system_error( (int)errc::result_out_of_range,
> generic_category(), "montor's locker count saturated" );
> assert((ref & ENTER_MASK) >= ref >> BITS);
> } while( !m_atomic.compare_exchange_strong( ref, ref + 1,
> memory_order_acquire, memory_order_relaxed ) );
> auto initThread = [&]()
> {
> m_threadId.store( &t_dummy, memory_order_relaxed );
> m_recCount.store( 0, memory_order_relaxed );
> };
> if( (ref & ENTER_MASK) == ref >> BITS ) [[likely]]
> return initThread();
> #if defined(_WIN32)
> if( WaitForSingleObject( m_xhEnterEvt.get(), INFINITE ) !=
> WAIT_OBJECT_0 )
> terminate();
> #elif defined(__unix__)
> if( semop( { { 0, -1, 0 } } ) )
> terminate();
> #endif
> initThread();
> }
>
> void monitor::unlock()
> {
> if( uint32_t rc; m_threadId.load( memory_order_relaxed ) ==
> &t_dummy && (rc = m_recCount.load( memory_order_relaxed )) )
> {
> m_recCount.store( rc - 1, memory_order_relaxed );
> return;
> }
> atomic_word_t ref = m_atomic.load( memory_order_relaxed );
> assert((ref & ENTER_MASK) && m_threadId == &t_dummy);
> m_threadId.store( nullptr, memory_order_relaxed );
> do
> assert((ref & ENTER_MASK) >= ref >> BITS);
> while( !m_atomic.compare_exchange_strong( ref, ref - 1,
> memory_order_release, memory_order_relaxed ) );
> if( (ref & ENTER_MASK) == 1 ) [[likely]]
> return;
> #if defined(_WIN32)
> if( !SetEvent( m_xhEnterEvt.get() ) )
> terminate();
> #elif defined(__unix__)
> if( semop( { { 0, 1, IPC_NOWAIT } } ) )
> terminate();
> #endif
> }
>
> void monitor::wait()
> {
> assert(m_threadId == &t_dummy && !m_recCount);
> m_threadId.store( nullptr, memory_order_relaxed );
> atomic_word_t ref = m_atomic.load( memory_order_relaxed );
> do
> assert((ref & ENTER_MASK) > ref >> BITS);
> while( !m_atomic.compare_exchange_strong( ref, ref + SIGNAL_VALUE,
> memory_order_release, memory_order_relaxed ) );
> if( (ref & ENTER_MASK) - (ref >> BITS) > 1 )
> {
> #if defined(_WIN32)
> if( !SetEvent( m_xhEnterEvt.get() ) )
> terminate();
> #elif defined(__unix__)
> if( semop( { { 0, 1, IPC_NOWAIT } } ) )
> terminate();
> #endif
> }
> #if defined(_WIN32)
> HANDLE waitFor[2] { m_xhEnterEvt.get(), m_xhSignalSem.get() };
> if( WaitForMultipleObjects( 2, waitFor, TRUE, INFINITE ) !=
> WAIT_OBJECT_0 )
> terminate();
> #elif defined(__unix__)
> if( semop( { { 0, -1, 0 }, { 1, -1, 0 } } ) )
> terminate();
> #endif
> m_threadId.store( &t_dummy, memory_order_relaxed );
> m_recCount.store( 0, memory_order_relaxed );
> }
>
> void monitor::notify()
> {
> atomic_word_t ref = m_atomic.load( memory_order_relaxed );
> assert((ref & ENTER_MASK) > ref >> BITS && m_threadId == &t_dummy);
> uint32_t n;
> while( (n = (uint32_t)(ref >> BITS)) &&
> !m_atomic.compare_exchange_strong( ref, ref - SIGNAL_VALUE,
> memory_order_relaxed, memory_order_relaxed ) );
> if( !(ref >> BITS) )
> return;
> #if defined(_WIN32)
> if( !ReleaseSemaphore( m_xhSignalSem.get(), 1, nullptr ) )
> terminate();
> #elif defined(__unix__)
> int ret;
> do
> ret = semop( { { 1, 1, IPC_NOWAIT } } );
> while( ret == EAGAIN );
while( ret == -1 && errno == EAGAIN );
> if( ret )
> terminate();
> #endif
> }
>
> void monitor::notify_all()
> {
> atomic_word_t ref = m_atomic.load( memory_order_relaxed );
> assert((ref & ENTER_MASK) > ref >> BITS && m_threadId == &t_dummy);
> uint32_t n;
> while( (n = (uint32_t)(ref >> BITS)) &&
> !m_atomic.compare_exchange_strong( ref, ref & ENTER_MASK,
> memory_order_relaxed, memory_order_relaxed ) );
> while( n )
> {
> uint32_t nRelease = n <= SEM_MAX ? n : SEM_MAX;
> #if defined(_WIN32)
> BOOL succ;
> for( ; !(succ = ReleaseSemaphore( m_xhSignalSem.get(),
> nRelease, nullptr )) && GetLastError() == ERROR_TOO_MANY_POSTS;
> nRelease = nRelease > 1 ? nRelease / 2 : nRelease );
> if( !succ )
> terminate();
> #elif defined(__unix__)
> int ret;
> for( ; (ret = semop( { { 1, (short)nRelease, IPC_NOWAIT } } ))
> == EAGAIN;
for( ; (ret = semop( { { 1, (short)nRelease, IPC_NOWAIT } } )) == -1 &&
errno == EAGAIN;
> nRelease = nRelease > 1 ? nRelease / 2 : nRelease );
> if( ret )
> terminate();
> #endif
> n -= nRelease;
> }
> }
>
> #if defined(__unix__)
> int monitor::semop( initializer_list<sembuf> sems )
> {
> int ret;
> while( (ret = ::semop( m_sems, const_cast<sembuf *>(sems.begin()),
> sems.size() )) == EINTR );
> return ret;
> }
> #endif
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 13:49 -0800 |
| Message-ID | <uigvpj$1q2i4$2@dont-email.me> |
| In reply to | #117661 |
On 11/8/2023 1:41 PM, Chris M. Thomasson wrote: > On 11/8/2023 9:16 AM, Bonita Montero wrote: >> Am 08.11.2023 um 15:56 schrieb Bonita Montero: >>> Java and .NET have monitor objects instead of a combination of mutexes >>> and condition variables. The advantage of a monitor object is that when >>> you wait for a monitor to be signalled you can wait for that and for the >>> mutexe's semaphore to be unlocked in _one_ step. With a condition varia- >>> ble you have first to wait for the notify()-semaphore to be signalled >>> and for the mutexe's lock in two steps. >>> The below code simply has a 32 or 64 bit atomic (depening on if the 64 >>> bit variant is lock-free or not) and the lower half is the number of >>> threads waiting to enter the mutex part and the upper half is the num- >>> ber of threads waiting to be notified. As all threads wanting to be >>> notified are also waiting for the mutex the lower half is always >= >>> the upper half, which I check for in several asserts. >>> On Windows waiting to be notified and waiting to lock the mutex part >>> to be unlocked is done by WaitForMultipleObjects(). On Linux there's >>> no way to wait for mutliple kernel handles to be signalled, but there >>> are SystemV semaphore sets which may consist of several semaphores and >>> you may have multiple operations to proceed atomically on this set. >>> The drawback of combining the mutex and condition-variable parts is >>> that you can't have multiple conditions associated with the same mutex. > > [snip code] > > Model it through Relacy Race Detector first, if you get any issues, we > can work through them. ;^) > > https://github.com/dvyukov/relacy > > There is no shame in using a race detector. If you want me to debug your work, well, its not going to be for free. Believe it or not its not exactly trivial. You already had to make corrections to your own code. > while( ret == -1 && errno == EAGAIN ); Keep EINTR in mind.
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2023-11-09 05:37 +0100 |
| Message-ID | <uihnm3$21tq7$4@raubtier-asyl.eternal-september.org> |
| In reply to | #117665 |
Am 08.11.2023 um 22:49 schrieb Chris M. Thomasson: > Keep EINTR in mind. EINTR is handled if you inspect my own semop overload function.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 20:40 -0800 |
| Message-ID | <uihnsr$21rab$2@dont-email.me> |
| In reply to | #117678 |
On 11/8/2023 8:37 PM, Bonita Montero wrote: > Am 08.11.2023 um 22:49 schrieb Chris M. Thomasson: > >> Keep EINTR in mind. > > EINTR is handled if you inspect my own semop overload function. > I actually might have some free time to blow on it later on tonight. Humm... You are not exactly a fun person to work for.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 20:39 -0800 |
| Message-ID | <uihnql$21rae$2@dont-email.me> |
| In reply to | #117665 |
On 11/8/2023 1:49 PM, Chris M. Thomasson wrote: > On 11/8/2023 1:41 PM, Chris M. Thomasson wrote: >> On 11/8/2023 9:16 AM, Bonita Montero wrote: >>> Am 08.11.2023 um 15:56 schrieb Bonita Montero: >>>> Java and .NET have monitor objects instead of a combination of mutexes >>>> and condition variables. The advantage of a monitor object is that when >>>> you wait for a monitor to be signalled you can wait for that and for >>>> the >>>> mutexe's semaphore to be unlocked in _one_ step. With a condition >>>> varia- >>>> ble you have first to wait for the notify()-semaphore to be signalled >>>> and for the mutexe's lock in two steps. >>>> The below code simply has a 32 or 64 bit atomic (depening on if the 64 >>>> bit variant is lock-free or not) and the lower half is the number of >>>> threads waiting to enter the mutex part and the upper half is the num- >>>> ber of threads waiting to be notified. As all threads wanting to be >>>> notified are also waiting for the mutex the lower half is always >= >>>> the upper half, which I check for in several asserts. >>>> On Windows waiting to be notified and waiting to lock the mutex part >>>> to be unlocked is done by WaitForMultipleObjects(). On Linux there's >>>> no way to wait for mutliple kernel handles to be signalled, but there >>>> are SystemV semaphore sets which may consist of several semaphores and >>>> you may have multiple operations to proceed atomically on this set. >>>> The drawback of combining the mutex and condition-variable parts is >>>> that you can't have multiple conditions associated with the same mutex. >> >> [snip code] >> >> Model it through Relacy Race Detector first, if you get any issues, we >> can work through them. ;^) >> >> https://github.com/dvyukov/relacy >> >> > > There is no shame in using a race detector. If you want me to debug your > work, well, its not going to be for free. Believe it or not its not > exactly trivial. You already had to make corrections to your own code. > > > while( ret == -1 && errno == EAGAIN ); > > Keep EINTR in mind. Wrt your code: https://youtu.be/0R6WIbx8ysE
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 13:41 -0800 |
| Message-ID | <uigv9g$1q2i4$1@dont-email.me> |
| In reply to | #117661 |
On 11/8/2023 9:16 AM, Bonita Montero wrote: > Am 08.11.2023 um 15:56 schrieb Bonita Montero: >> Java and .NET have monitor objects instead of a combination of mutexes >> and condition variables. The advantage of a monitor object is that when >> you wait for a monitor to be signalled you can wait for that and for the >> mutexe's semaphore to be unlocked in _one_ step. With a condition varia- >> ble you have first to wait for the notify()-semaphore to be signalled >> and for the mutexe's lock in two steps. >> The below code simply has a 32 or 64 bit atomic (depening on if the 64 >> bit variant is lock-free or not) and the lower half is the number of >> threads waiting to enter the mutex part and the upper half is the num- >> ber of threads waiting to be notified. As all threads wanting to be >> notified are also waiting for the mutex the lower half is always >= >> the upper half, which I check for in several asserts. >> On Windows waiting to be notified and waiting to lock the mutex part >> to be unlocked is done by WaitForMultipleObjects(). On Linux there's >> no way to wait for mutliple kernel handles to be signalled, but there >> are SystemV semaphore sets which may consist of several semaphores and >> you may have multiple operations to proceed atomically on this set. >> The drawback of combining the mutex and condition-variable parts is >> that you can't have multiple conditions associated with the same mutex. [snip code] Model it through Relacy Race Detector first, if you get any issues, we can work through them. ;^) https://github.com/dvyukov/relacy
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2023-11-09 05:36 +0100 |
| Message-ID | <uihnkl$21tq7$3@raubtier-asyl.eternal-september.org> |
| In reply to | #117667 |
Am 08.11.2023 um 22:41 schrieb Chris M. Thomasson: > Model it through Relacy Race Detector first, if you get any issues, we > can work through them. ;^) > https://github.com/dvyukov/relacy You'd suggest Relacy for a hello world.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-11-08 20:41 -0800 |
| Message-ID | <uihnu3$21rab$3@dont-email.me> |
| In reply to | #117677 |
On 11/8/2023 8:36 PM, Bonita Montero wrote: > Am 08.11.2023 um 22:41 schrieb Chris M. Thomasson: > >> Model it through Relacy Race Detector first, if you get any issues, we >> can work through them. ;^) >> https://github.com/dvyukov/relacy > > You'd suggest Relacy for a hello world. > > :^D Hello world! Try to get it passing a Relacy test, if you are having trouble, I can help you.
[toc] | [prev] | [next] | [standalone]
Page 11 of 13 — ← Prev page 1 … 9 10 [11] 12 13 Next page →
Back to top | Article view | comp.lang.c++
csiph-web