Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #124999 > unrolled thread
| Started by | Lynn McGuire <lynnmcguire5@gmail.com> |
|---|---|
| First post | 2026-10-13 23:18 -0500 |
| Last post | 2026-11-02 10:30 +0100 |
| Articles | 20 on this page of 529 — 48 participants |
Back to article view | Back to comp.lang.c++
“The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-13 23:18 -0500
Re: “The end of software secrecy is almost upon us" Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-14 18:30 +0800
Transpiling from Pascal to Rust (was: Re: “The end of software secrecy is almost upon us") ram@zedat.fu-berlin.de (Stefan Ram) - 2026-10-14 11:35 +0000
Re: “The end of software secrecy is almost upon us" "De ongekruisigde ds." <ongekruisigde-ds@invalid.invalid> - 2026-10-14 11:37 +0000
Re: “The end of software secrecy is almost upon us" Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-14 19:59 +0800
Re: “The end of software secrecy is almost upon us" Peter Flass <Peter@Iron-Spring.com> - 2026-10-14 07:35 -0700
Re: Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-14 11:57 -0400
Re: “The end of software secrecy is almost upon us" Cryptoengineer <petertrei@gmail.com> - 2026-10-14 13:07 -0400
Re: “The end of software secrecy is almost upon us" Gary Scott <garylscott@sbcglobal.net> - 2026-10-14 14:04 -0500
Re: “The end of software secrecy is almost upon us" Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-14 19:34 +0000
Re: “The end of software secrecy is almost upon us" Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-15 05:55 +0800
Re: Re: “The end of software secrecy is almost upon us" ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-10-14 22:11 +0000
Re: Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-14 20:42 -0400
Re: “The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-14 21:43 -0500
Re: Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-15 11:22 -0400
Re: “The end of software secrecy is almost upon us" Gary Scott <garylscott@sbcglobal.net> - 2026-10-15 10:40 -0500
Re: “The end of software secrecy is almost upon us" Thomas Koenig <tkoenig@netcologne.de> - 2026-10-18 09:20 +0000
Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-18 10:34 -0400
Re: “The end of software secrecy is almost upon us" Thomas Koenig <tkoenig@netcologne.de> - 2026-10-19 06:57 +0000
Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-19 15:44 -0400
Re: “The end of software secrecy is almost upon us" Thomas Koenig <tkoenig@netcologne.de> - 2026-10-19 20:09 +0000
Re: “The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-19 16:10 -0500
Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-19 18:08 -0400
Re: “The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-19 17:10 -0500
Re: Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-19 18:57 -0400
Re: “The end of software secrecy is almost upon us" Thomas Koenig <tkoenig@netcologne.de> - 2026-10-20 05:28 +0000
Re: “The end of software secrecy is almost upon us" Titus G <noone@nowhere.com> - 2026-10-20 18:46 +1300
Re: “The end of software secrecy is almost upon us" Cryptoengineer <petertrei@gmail.com> - 2026-10-20 13:20 -0400
Re: “The end of software secrecy is almost upon us" Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-21 01:27 +0800
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-20 18:14 +0000
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-20 14:22 -0400
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-20 18:29 +0000
Re: “The end of software secrecy is almost upon Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-20 15:06 -0500
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-20 20:20 +0000
Re: The end of software secrecy is almost upon Rosario19 <Ros@invalid.invalid> - 2026-11-02 10:54 +0100
Re: The end of software secrecy is almost upon "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2026-11-02 11:11 +0100
Re: The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-11-02 16:51 +0000
Re: The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-02 20:06 +0000
Re: The end of software secrecy is almost upon Rosario19 <Ros@invalid.invalid> - 2026-11-07 13:35 +0100
Re: “The end of software secrecy is almost upon William Hyde <wthyde1953@gmail.com> - 2026-10-20 19:32 -0400
Re: Re: “The end of software secrecy is almost upon John Levine <johnl@taugh.com> - 2026-10-21 03:31 +0000
Re: Re: “The end of software secrecy is almost upon ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-10-21 04:31 +0000
Re: “The end of software secrecy is almost upon Radey Shouman <shouman@comcast.net> - 2026-10-21 10:41 -0400
Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-21 14:53 +0000
Re: “The end of software secrecy is almost upon drb@ihatespam.msu.edu (Dennis Boone) - 2026-10-21 15:57 +0000
Re: “The end of software secrecy is almost upon ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-10-21 16:02 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 00:37 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-22 11:05 +0800
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-21 20:07 -0700
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-22 14:22 +0800
Re: “The end of software secrecy is almost upon ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-10-22 04:22 +0000
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-21 07:37 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-21 12:17 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 00:36 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-22 09:21 +0800
Re: “The end of software secrecy is almost upon Cryptoengineer <petertrei@gmail.com> - 2026-10-20 16:40 -0400
Re: The end of software secrecy is almost upon Rosario19 <Ros@invalid.invalid> - 2026-11-02 10:58 +0100
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-20 19:04 +0000
Re: “The end of software secrecy is almost upon Thomas Koenig <tkoenig@netcologne.de> - 2026-10-20 19:54 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-20 20:00 +0000
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-20 23:18 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-21 01:27 +0000
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-21 03:22 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-21 05:35 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-21 20:09 +0800
Re: The end of software secrecy is almost upon Rosario19 <Ros@invalid.invalid> - 2026-11-06 12:43 +0100
Re: The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-06 16:38 +0000
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-20 23:20 +0000
Re: “The end of software secrecy is almost upon Cryptoengineer <petertrei@gmail.com> - 2026-10-20 16:49 -0400
Re: “The end of software secrecy is almost upon Nuno Silva <nunojsilva@invalid.invalid> - 2026-10-21 01:15 +0100
Re: Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-20 20:49 +0000
Re: “The end of software secrecy is almost upon us" William Hyde <wthyde1953@gmail.com> - 2026-10-20 14:36 -0400
Re: “The end of software secrecy is almost upon us" Titus G <noone@nowhere.com> - 2026-10-21 16:11 +1300
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-21 05:37 +0000
Re: “The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-20 00:48 -0500
Re: Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-20 09:39 -0400
Re: “The end of software secrecy is almost upon us" Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-20 21:51 +0800
Re: “The end of software secrecy is almost upon us" Thomas Koenig <tkoenig@netcologne.de> - 2026-10-20 15:50 +0000
Re: Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-20 16:41 -0400
Re: “The end of software secrecy is almost upon us" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-20 16:48 -0700
Re: “The end of software secrecy is almost upon us" William Hyde <wthyde1953@gmail.com> - 2026-10-20 14:48 -0400
Re: “The end of software secrecy is almost upon us" Thomas Koenig <tkoenig@netcologne.de> - 2026-10-20 17:15 +0000
Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-20 17:24 +0000
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-20 20:50 +0200
Re: “The end of software secrecy is almost upon Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-10-20 19:06 -0700
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-21 07:47 +0000
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-21 11:06 -0400
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-21 23:10 +0800
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-21 12:29 -0400
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-21 17:50 +0000
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-21 14:12 -0700
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-22 14:51 +0000
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-22 12:19 -0400
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 08:01 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-23 16:15 +0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 08:16 +0000
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-23 09:06 -0700
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-23 16:37 +0000
Re: “The end of software secrecy is almost upon John Ames <commodorejohn@gmail.com> - 2026-10-23 10:32 -0700
Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-23 14:09 -0400
Re: “The end of software secrecy is almost upon John Ames <commodorejohn@gmail.com> - 2026-10-23 12:02 -0700
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-23 20:36 +0000
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-23 20:28 +0000
Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-24 13:47 -0400
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-24 21:38 +0000
Re: �The end of software secrecy is almost upon Jerry Brown <jerry@jwbrown.co.uk.invalid> - 2026-10-25 08:11 +0000
Re: The end of software secrecy is almost upon Thomas Koenig <tkoenig@netcologne.de> - 2026-10-25 09:30 +0000
Re: The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-25 08:37 -0700
Re: The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-25 08:42 -0700
Re: ?The end of software secrecy is almost upon Jerry Brown <jerry@jwbrown.co.uk.invalid> - 2026-10-26 07:59 +0000
Re: ?The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-26 10:33 +0000
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 19:30 +0000
Re: “The end of software secrecy is almost upon us" Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-23 20:28 +0000
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 22:50 +0000
Re: “The end of software secrecy is almost upon us" boltar@caprica.universe - 2026-10-24 08:18 +0000
Re: “The end of software secrecy is almost upon Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-23 14:49 -0500
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 19:59 +0000
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-24 08:20 +0000
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-24 13:53 -0400
Re: “The end of software secrecy is almost upon Blaine <cactus_DAC@yahoo.com> - 2026-10-24 12:07 -0600
Re: “The end of software secrecy is almost upon Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2026-10-25 08:22 +0000
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 08:32 +0000
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-25 08:10 -0400
Re: “The end of software secrecy is almost upon Cryptoengineer <petertrei@gmail.com> - 2026-10-25 13:58 -0400
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-25 19:06 -0400
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 17:07 -0700
Re: “The end of software secrecy is almost upon Cryptoengineer <petertrei@gmail.com> - 2026-10-25 22:54 -0400
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 03:47 +0000
Re: “The end of software secrecy is almost upon Peter Moylan <peter@pmoylan.org> - 2026-10-26 08:29 +1100
Re: Re: “The end of software secrecy is almost upon Rich Alderson <news@alderson.users.panix.com> - 2026-10-25 20:10 -0400
Re: “The end of software secrecy is almost upon "Gary R. Schmidt" <grschmidt@acm.org> - 2026-10-25 01:03 +1100
Re: “The end of software secrecy is almost upon Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-26 17:08 -0500
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-23 14:01 -0400
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 13:02 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 22:57 +0000
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-23 23:31 +0000
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-23 17:04 -0700
Re: “The end of software secrecy is almost upon us” Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-24 03:44 +0000
Re: “The end of software secrecy is almost upon us” "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-24 13:04 -0700
Re: “The end of software secrecy is almost upon us” Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-24 21:38 +0000
Re: “The end of software secrecy is almost upon us” "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 19:43 -0700
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-22 19:05 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-22 22:48 +0300
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 08:05 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-23 11:42 +0300
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 09:18 +0000
Re: “The end of software secrecy is almost upon Cryptoengineer <petertrei@gmail.com> - 2026-10-23 12:57 -0400
Re: Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-23 18:24 +0000
Whilst All The Computer Experts are Visiting r.a.sf.w. Titus G <noone@nowhere.com> - 2026-10-24 16:12 +1300
Re: Whilst All The Computer Experts are Visiting r.a.sf.w. Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-24 15:22 +0800
Re: “The end of software secrecy is almost upon William Hyde <wthyde1953@gmail.com> - 2026-10-23 17:40 -0400
Re: “The end of software secrecy is almost upon James Kuyper <jameskuyper@alumni.caltech.edu> - 2026-10-23 18:50 -0400
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 16:56 -0700
Re: “The end of software secrecy is almost upon Cryptoengineer <petertrei@gmail.com> - 2026-10-22 16:27 -0400
Re: “The end of software secrecy is almost upon Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-22 15:36 -0500
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-21 19:20 -0400
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-21 17:57 +0200
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-21 18:02 +0000
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-21 20:26 +0200
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-21 18:48 +0000
Re: Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-21 19:01 +0000
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-22 14:50 +0000
Re: Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-22 16:02 +0000
Re: “The end of software secrecy is almost upon James Kuyper <jameskuyper@alumni.caltech.edu> - 2026-10-22 16:25 -0400
Re: Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-22 22:01 +0000
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-23 11:28 +0200
Re: “The end of software secrecy is almost upon James Kuyper <jameskuyper@alumni.caltech.edu> - 2026-10-23 10:21 -0400
Re: Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-23 20:49 +0000
Re: “The end of software secrecy is almost upon Nuno Silva <nunojsilva@invalid.invalid> - 2026-10-23 00:23 +0100
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-23 00:41 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-23 12:06 +0300
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 07:58 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-23 16:06 +0800
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-23 11:56 +0300
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-23 17:15 +0800
Re: Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-22 16:22 +0000
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 08:03 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 12:58 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 14:06 -0700
Re: Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-23 20:45 +0000
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-24 08:21 +0000
Re: Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-24 14:25 +0000
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-24 14:51 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-24 22:55 +0800
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-24 13:07 -0700
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-24 07:26 -0700
Re: Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-24 13:57 -0400
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 08:34 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 14:19 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-26 10:01 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:03 -0700
Re: “The end of software secrecy is almost upon us” Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 21:59 +0000
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-28 09:01 +0000
Re: “The end of software secrecy is almost upon Blaine <cactus_DAC@yahoo.com> - 2026-10-28 09:47 -0600
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-28 14:04 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-29 16:19 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-29 12:49 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-30 11:21 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-26 22:09 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 20:16 -0700
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-28 09:08 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-28 22:05 +0200
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-29 16:16 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 14:21 -0700
Re: Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-24 16:41 +0000
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-24 12:17 -0700
Re: Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-24 21:24 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-25 01:11 +0300
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-25 00:28 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-25 08:42 +0200
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-25 13:32 +0000
Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-25 15:59 +0000
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-25 16:15 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 16:29 +0000
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-25 17:18 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-26 09:54 +0000
Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-26 09:50 -0400
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-26 16:58 +0000
Re: “The end of software secrecy is almost upon kludge@panix.com (Scott Dorsey) - 2026-10-26 15:32 -0400
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 14:31 -0700
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 08:41 +0000
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-25 13:34 +0000
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-25 08:41 -0700
Re: Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-25 17:06 +0000
Re: “The end of software secrecy is almost upon Robert Woodward <robertaw@drizzle.com> - 2026-10-25 10:19 -0700
Re: âThe end of software secrecy is almost upon Cryptoengineer <petertrei@gmail.com> - 2026-10-25 14:03 -0400
Re: âThe end of software secrecy is almost upon Blaine <cactus_DAC@yahoo.com> - 2026-10-25 12:21 -0600
Re: âThe end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-25 19:26 +0100
Re: âThe end of software secrecy is almost upon Blaine <cactus_DAC@yahoo.com> - 2026-10-25 12:29 -0600
Re: âThe end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-25 19:59 +0100
Re: âThe end of software secrecy is almost upon Titus G <noone@nowhere.com> - 2026-10-26 09:43 +1300
Re: âThe end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-25 19:54 -0700
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 16:13 +0000
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-25 16:17 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 16:32 +0000
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-25 17:14 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-26 09:51 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-26 22:04 +0200
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-28 09:06 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-28 21:47 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-28 14:09 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-29 16:20 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-29 23:07 +0200
Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-29 22:26 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-30 00:54 +0200
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-30 02:22 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-30 10:59 +0200
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-30 11:25 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-30 15:23 +0200
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-30 16:07 +0000
Re: “The end of software secrecy is almost upon Jeroen Belleman <jeroen@nospam.please> - 2026-10-30 20:37 +0100
Re: “The end of software secrecy is almost upon us” Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-30 22:35 +0000
Re: “The end of software secrecy is almost upon us” Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-31 04:14 +0000
Re: “The end of software secrecy is almost upon us” Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-31 05:37 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-31 09:47 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-31 19:56 +0200
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-01 08:32 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-11-01 21:59 +0200
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-02 15:43 +0000
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-11-02 16:51 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-04 08:48 +0000
Re: “The end of software secrecy is almost upon Jeroen Belleman <jeroen@nospam.please> - 2026-11-04 11:24 +0100
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-04 16:24 +0000
Re: “The end of software secrecy is almost upon Jeroen Belleman <jeroen@nospam.please> - 2026-11-04 23:53 +0100
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-11-06 15:38 +0200
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-06 16:39 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-11-02 23:46 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 15:02 -0800
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 15:03 -0800
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-11-03 21:51 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-03 13:10 -0800
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-04 08:54 +0000
Re: “The end of software secrecy is almost upon antispam@fricas.org (Waldek Hebisch) - 2026-11-07 01:17 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-07 09:41 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-11-07 20:20 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-07 12:19 -0800
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-08 09:10 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 15:00 -0800
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 14:59 -0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-04 08:54 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-04 02:22 -0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-04 16:22 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-04 10:56 -0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-04 19:53 +0000
Re: “The end of software secrecy is almost upon Gary Scott <garylscott@sbcglobal.net> - 2026-11-04 14:17 -0600
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-04 02:24 -0800
Re: “The end of software secrecy is almost upon us” Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-11-01 19:40 +0000
Re: “The end of software secrecy is almost upon us” "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 15:06 -0800
Re: “The end of software secrecy is almost upon us” Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-11-03 02:42 +0000
Re: “The end of software secrecy is almost upon us” "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 21:09 -0800
Re: “The end of software secrecy is almost upon us” "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 21:11 -0800
Re: “The end of software secrecy is almost upon us” Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-11-03 07:15 +0000
Re: “The end of software secrecy is almost upon us” "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-06 19:22 -0800
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-31 09:45 +0000
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-31 09:38 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-31 13:11 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-01 08:33 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-01 18:03 -0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-02 15:44 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 14:34 -0800
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-31 13:14 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-01 08:34 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-01 18:04 -0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-11-02 15:45 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 14:33 -0800
Threads and processes (was: Re: "The end of software secrecy is almost upon) Nuno Silva <nunojsilva@invalid.invalid> - 2026-10-25 23:48 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-25 22:56 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 17:22 -0700
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-26 09:59 +0000
Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-26 14:41 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-26 16:16 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-26 21:45 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:12 -0700
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-26 22:40 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:44 -0700
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-28 08:58 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-28 14:05 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-28 14:06 -0700
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-29 00:06 +0200
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-29 16:22 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-29 22:39 +0200
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-29 15:13 -0700
Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-29 22:25 +0000
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-30 02:10 +0000
Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-30 11:25 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-30 11:05 -0700
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-11-02 06:17 +0800
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-02 14:54 -0800
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:05 -0700
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-25 10:45 +0100
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 20:44 -0700
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-27 09:06 +0100
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-27 10:22 +0200
Re: “The end of software secrecy is almost upon cross@spitfire.i.gajendra.net (Dan Cross) - 2026-10-27 10:40 +0000
Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-27 15:03 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-04 02:34 -0800
Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-25 15:56 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 19:20 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 08:37 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-25 22:24 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 19:01 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 08:42 +0000
Re: what's a process, was The end of software secrecy is almost upon John Levine <johnl@taugh.com> - 2026-10-25 18:17 +0000
Re: Re: what's a process, was The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-26 09:57 +0000
Re: Re: what's a process, was The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-26 03:53 -0700
Re: Re: what's a process, was The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-26 14:44 +0000
Re: what's a process, was The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-26 08:56 -0700
Re: Re: what's a process, was The end of software secrecy is almost boltar@caprica.universe - 2026-10-26 16:19 +0000
Re: what's a process, was The end of software secrecy is almost Peter Flass <Peter@Iron-Spring.com> - 2026-10-26 11:46 -0700
Re: what's a process, was The end of software secrecy is almost "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:19 -0700
Re: what's a process, was The end of software secrecy is almost "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:19 -0700
Re: what's a process, was The end of software secrecy is almost boltar@caprica.universe - 2026-10-28 09:09 +0000
Re: what's a process, was The end of software secrecy is almost "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-28 14:10 -0700
Re: what's a process, was The end of software secrecy is almost upon Lynn Wheeler <lynn@garlic.com> - 2026-10-26 13:36 -1000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 19:03 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-24 13:12 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-25 08:31 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 14:22 -0700
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-26 10:02 +0000
Re: “The end of software secrecy is almost upon Blaine <cactus_DAC@yahoo.com> - 2026-10-26 13:10 -0600
Re: “The end of software secrecy is almost upon Titus G <noone@nowhere.com> - 2026-10-27 08:43 +1300
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-28 08:57 +0000
Re: “The end of software secrecy is almost upon Blaine <cactus_DAC@yahoo.com> - 2026-10-28 08:39 -0600
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:20 -0700
Threads and processes (Re: “The end of software secrecy is almost upon) Lars Poulsen <lars@beagle-ears.com> - 2026-10-26 19:14 -0700
Re: Threads and processes (Re: “The end of software secrecy is almost upon) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-27 06:08 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-22 09:51 +0800
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-22 14:54 +0000
Re: “The end of software secrecy is almost upon Michael S <already5chosen@yahoo.com> - 2026-10-22 22:44 +0300
Re: “The end of software secrecy is almost upon Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-22 15:41 -0500
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 03:21 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-22 22:31 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 06:27 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 12:48 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 19:56 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 13:30 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 12:57 -0700
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-23 11:34 +0200
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 10:11 +0000
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-23 09:55 -0700
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 19:25 +0000
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-24 12:38 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 12:55 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 22:46 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 16:58 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 17:00 -0700
Re: “The end of software secrecy is almost upon us” Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-24 03:39 +0000
Re: “The end of software secrecy is almost upon us” "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 19:51 -0700
Re: “The end of software secrecy is almost upon us” Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-27 05:56 +0000
Re: “The end of software secrecy is almost upon us” "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-04 02:36 -0800
Re: “The end of software secrecy is almost upon Thomas Koenig <tkoenig@netcologne.de> - 2026-10-23 21:00 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-24 05:14 +0800
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 22:49 +0000
Re: “The end of software secrecy is almost upon us" Andreas Eder <a_eder_muc@web.de> - 2026-10-25 16:31 +0100
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-25 20:07 +0000
Re: “The end of software secrecy is almost upon us" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 14:36 -0700
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-23 16:02 +0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 08:14 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-23 16:22 +0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 09:15 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-23 18:15 +0800
Re: Re: “The end of software secrecy is almost upon boltar@caprica.universe - 2026-10-23 08:10 +0000
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-22 09:20 +0200
Re: Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-22 14:58 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-23 03:52 +0800
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-04 02:38 -0800
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-20 12:11 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-21 01:29 +0000
Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-21 07:42 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-21 07:55 +0000
Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-21 08:05 +0000
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-21 07:41 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 00:40 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 00:23 +0000
Re: “The end of software secrecy is almost upon boltar@battlestar.co.uk - 2026-10-22 14:53 +0000
Re: “The end of software secrecy is almost upon Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-22 19:05 +0000
Re: “The end of software secrecy is almost upon Thomas Koenig <tkoenig@netcologne.de> - 2026-10-21 13:27 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 00:24 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-22 09:14 +0800
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 02:00 +0000
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-22 02:17 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 03:35 +0000
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-22 04:33 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 04:50 +0000
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-22 04:56 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-22 14:34 +0800
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-22 07:31 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-22 16:40 +0800
Re: “The end of software secrecy is almost upon James Kuyper <jameskuyper@alumni.caltech.edu> - 2026-10-22 11:18 -0400
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 03:33 +0000
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-23 04:10 +0000
Re: “The end of software secrecy is almost upon Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-10-22 21:21 -0700
Re: “The end of software secrecy is almost upon Thomas Koenig <tkoenig@netcologne.de> - 2026-10-23 05:43 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 06:29 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 04:22 +0000
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-23 05:54 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 19:20 +0000
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-23 19:38 +0000
Re: “The end of software secrecy is almost upon Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-24 05:19 +0800
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-22 07:26 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 03:19 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-22 22:29 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 06:25 +0000
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-23 11:45 +0200
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-23 09:57 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 13:43 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 13:50 -0700
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-24 12:43 +0200
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 19:29 -0700
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-23 09:02 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 19:19 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 13:56 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 22:42 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 17:01 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-24 03:33 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-24 13:26 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-24 13:27 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-24 22:32 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 19:57 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 20:09 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-24 22:32 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 19:28 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 03:43 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:23 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 21:46 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 14:51 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 14:29 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-23 22:43 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 17:01 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-23 14:00 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 16:16 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 00:42 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 19:11 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 03:39 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:26 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 21:45 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 14:47 -0700
Re: “The end of software secrecy is almost upon James Kuyper <jameskuyper@alumni.caltech.edu> - 2026-10-27 11:00 -0400
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-27 09:41 -0700
Re: Re: “The end of software secrecy is almost upon scott@slp53.sl.home (Scott Lurndal) - 2026-10-27 18:36 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-04 02:48 -0800
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-27 22:22 +0000
Re: “The end of software secrecy is almost upon James Kuyper <jameskuyper@alumni.caltech.edu> - 2026-10-27 21:35 -0400
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-28 01:43 +0000
Re: “The end of software secrecy is almost upon James Kuyper <jameskuyper@alumni.caltech.edu> - 2026-10-27 22:18 -0400
Re: “The end of software secrecy is almost upon Peter Flass <Peter@Iron-Spring.com> - 2026-10-27 19:28 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-28 14:16 -0700
Re: Structured Programming (was Re: “The end of software secrecy is almost upon us”) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-01 23:38 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-25 19:21 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 03:40 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:29 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 13:33 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 21:45 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 14:53 -0700
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-26 22:20 +0000
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 15:42 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 16:06 -0700
Re: “The end of software secrecy is almost upon David Brown <david.brown@hesbynett.no> - 2026-10-26 22:29 +0100
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 14:58 -0700
Re: “The end of software secrecy is almost upon "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 15:46 -0700
Re: “The end of software secrecy is almost upon Thomas Koenig <tkoenig@netcologne.de> - 2026-10-22 03:46 +0000
Re: “The end of software secrecy is almost upon Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-22 04:51 +0000
Re: “The end of software secrecy is almost upon Thomas Koenig <tkoenig@netcologne.de> - 2026-10-22 06:39 +0000
Re: “The end of software secrecy is almost upon Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-10-22 16:54 -0700
Re: “The end of software secrecy is almost upon "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> - 2026-10-23 01:57 +0000
Re: “The end of software secrecy is almost upon us" Peter Flass <Peter@Iron-Spring.com> - 2026-10-20 12:10 -0700
Re: “The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-20 15:20 -0500
Re: “The end of software secrecy is almost upon us" Thomas Koenig <tkoenig@netcologne.de> - 2026-10-20 21:20 +0000
Re: “The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-20 16:26 -0500
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-21 01:35 +0000
Re: “The end of software secrecy is almost upon us" Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-21 01:30 +0000
Re: “The end of software secrecy is almost upon us" Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-21 20:21 +0800
Re: “The end of software secrecy is almost upon us" Cryptoengineer <petertrei@gmail.com> - 2026-10-20 17:03 -0400
Re: “The end of software secrecy is almost upon us" Blaine <cactus_DAC@yahoo.com> - 2026-10-19 16:26 -0600
Re: Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-19 19:01 -0400
Re: “The end of software secrecy is almost upon us" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-19 13:09 -0700
Re: “The end of software secrecy is almost upon us" WolfFan <akwolffan@zoho.com> - 2026-10-14 08:52 -0400
Re: âThe end of software secrecy is almost upon us" Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-15 06:15 +0800
Re: “The end of software secrecy is almost upon us" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-14 14:26 -0700
Re: The_end_of_software_secrecy_is_almost_upon_us legalize+jeeves@mail.xmission.com (Richard) - 2026-10-15 14:56 +0000
Re: The_end_of_software_secrecy_is_almost_upon_us Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-15 14:07 -0500
Re: The_end_of_software_secrecy_is_almost_upon_us ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-10-15 19:18 +0000
Re: The_end_of_software_secrecy_is_almost_upon_us Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-15 15:02 -0500
Re: “The end of software secrecy is almost upon us" kludge@panix.com (Scott Dorsey) - 2026-10-15 11:05 -0400
Re: “The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-15 14:13 -0500
Re: “The end of software secrecy is almost upon us" Jay Morris <morrisj@epsilon3.me> - 2026-10-15 20:35 -0500
Re: “The end of software secrecy is almost upon us" Lynn McGuire <lynnmcguire5@gmail.com> - 2026-10-24 00:27 -0500
Re: “The end of software secrecy is almost upon us" John Smith <invalid@invalid.invalid> - 2026-10-30 05:04 +0000
Re: “The end of software secrecy is almost upon us" Bonita Montero <Bonita.Montero@gmail.com> - 2026-11-02 10:30 +0100
Page 23 of 27 — ← Prev page 1 … 21 22 [23] 24 25 … 27 Next page →
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-23 03:19 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bejnh$1eab6$1@dont-email.me> |
| In reply to | #125166 |
On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote: > That's why I try to use PL/I AUTOMATIC (stack) storage and not > allocate a lot of stuff. You need to have a disciplined approach if > you allocate random stuff here and there. What if you’re building an object that needs to be returned to the caller?
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-22 22:29 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11berc9$1ge43$1@dont-email.me> |
| In reply to | #125191 |
On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote: > On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote: > >> That's why I try to use PL/I AUTOMATIC (stack) storage and not >> allocate a lot of stuff. You need to have a disciplined approach if >> you allocate random stuff here and there. > > What if you’re building an object that needs to be returned to the > caller? Have the caller have the object before hand and call a function to initialize it?
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-23 06:25 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11beuk5$1h9da$2@dont-email.me> |
| In reply to | #125197 |
On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote: > On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote: >> >> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote: >> >>> That's why I try to use PL/I AUTOMATIC (stack) storage and not >>> allocate a lot of stuff. You need to have a disciplined approach >>> if you allocate random stuff here and there. >> >> What if you’re building an object that needs to be returned to the >> caller? > > Have the caller have the object before hand and call a function to > initialize it? I’m assuming that all that BASIC programming hasn’t got to your head, and you’re not serious. ;)
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2026-10-23 11:45 +0200 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bfacd$1jkb5$6@dont-email.me> |
| In reply to | #125201 |
On 23/10/2026 08:25, Lawrence D’Oliveiro wrote:
> On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:
>
>> On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote:
>>>
>>> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:
>>>
>>>> That's why I try to use PL/I AUTOMATIC (stack) storage and not
>>>> allocate a lot of stuff. You need to have a disciplined approach
>>>> if you allocate random stuff here and there.
>>>
>>> What if you’re building an object that needs to be returned to the
>>> caller?
>>
>> Have the caller have the object before hand and call a function to
>> initialize it?
>
> I’m assuming that all that BASIC programming hasn’t got to your head,
> and you’re not serious. ;)
Chris' wording is perhaps poor, but the principle is right.
I don't know PL/I or Fortran, but in C if you have :
typedef struct data_struct { int a; int xs[20]; } S ;
S build_some_data(void) {
S s;
s.a = 123;
for (int i = 0; i < 20; i++) s.xs[i] = i;
return s;
}
void foo() {
S s = build_some_data();
}
then it is typically handled as though you had written :
void build_some_data(S * p) {
p->a = 123;
for (int i = 0; i < 20; i++) p->xs[i] = i;
return;
}
void foo() {
S s;
build_some_data(&s);
}
That is - the caller creates the /space/ for the returned object, but
does not do any kind of initialisation. It passes a pointer to that
space as a hidden parameter to the function that wants to return the object.
That principle should work fine in any language, as long as the size of
the returned object is known by the caller code.
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <Peter@Iron-Spring.com> |
|---|---|
| Date | 2026-10-23 09:57 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bg3kt$203lc$2@dont-email.me> |
| In reply to | #125223 |
On 10/23/26 02:45, David Brown wrote:
> On 23/10/2026 08:25, Lawrence D’Oliveiro wrote:
>> On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:
>>
>>> On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote:
>>>>
>>>> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:
>>>>
>>>>> That's why I try to use PL/I AUTOMATIC (stack) storage and not
>>>>> allocate a lot of stuff. You need to have a disciplined approach
>>>>> if you allocate random stuff here and there.
>>>>
>>>> What if you’re building an object that needs to be returned to the
>>>> caller?
>>>
>>> Have the caller have the object before hand and call a function to
>>> initialize it?
>>
>> I’m assuming that all that BASIC programming hasn’t got to your head,
>> and you’re not serious. ;)
>
> Chris' wording is perhaps poor, but the principle is right.
>
> I don't know PL/I or Fortran, but in C if you have :
>
> typedef struct data_struct { int a; int xs[20]; } S ;
>
> S build_some_data(void) {
> S s;
>
> s.a = 123;
> for (int i = 0; i < 20; i++) s.xs[i] = i;
>
> return s;
> }
>
> void foo() {
> S s = build_some_data();
> }
>
>
> then it is typically handled as though you had written :
>
> void build_some_data(S * p) {
> p->a = 123;
> for (int i = 0; i < 20; i++) p->xs[i] = i;
>
> return;
> }
>
> void foo() {
> S s;
> build_some_data(&s);
> }
>
>
> That is - the caller creates the /space/ for the returned object, but
> does not do any kind of initialisation. It passes a pointer to that
> space as a hidden parameter to the function that wants to return the
> object.
>
> That principle should work fine in any language, as long as the size of
> the returned object is known by the caller code.
That last sentence is why it would not work fine,
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-23 13:43 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bggtm$25go8$1@dont-email.me> |
| In reply to | #125232 |
On 10/23/2026 9:57 AM, Peter Flass wrote:
> On 10/23/26 02:45, David Brown wrote:
>> On 23/10/2026 08:25, Lawrence D’Oliveiro wrote:
>>> On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:
>>>
>>>> On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote:
>>>>>
>>>>> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:
>>>>>
>>>>>> That's why I try to use PL/I AUTOMATIC (stack) storage and not
>>>>>> allocate a lot of stuff. You need to have a disciplined approach
>>>>>> if you allocate random stuff here and there.
>>>>>
>>>>> What if you’re building an object that needs to be returned to the
>>>>> caller?
>>>>
>>>> Have the caller have the object before hand and call a function to
>>>> initialize it?
>>>
>>> I’m assuming that all that BASIC programming hasn’t got to your head,
>>> and you’re not serious. ;)
>>
>> Chris' wording is perhaps poor, but the principle is right.
>>
>> I don't know PL/I or Fortran, but in C if you have :
>>
>> typedef struct data_struct { int a; int xs[20]; } S ;
>>
>> S build_some_data(void) {
>> S s;
>>
>> s.a = 123;
>> for (int i = 0; i < 20; i++) s.xs[i] = i;
>>
>> return s;
>> }
>>
>> void foo() {
>> S s = build_some_data();
>> }
>>
>>
>> then it is typically handled as though you had written :
>>
>> void build_some_data(S * p) {
>> p->a = 123;
>> for (int i = 0; i < 20; i++) p->xs[i] = i;
>>
>> return;
>> }
>>
>> void foo() {
>> S s;
>> build_some_data(&s);
>> }
>>
>>
>> That is - the caller creates the /space/ for the returned object, but
>> does not do any kind of initialisation. It passes a pointer to that
>> space as a hidden parameter to the function that wants to return the
>> object.
>>
>> That principle should work fine in any language, as long as the size
>> of the returned object is known by the caller code.
>
> That last sentence is why it would not work fine,
if a dynamic object is returned, we need to handle its lifetime.
__________________________
// pseudo code
struct foo
{
struct bar* m_bar = nullptr;
int m_a = 0;
double m_b = .42;
};
foo_init(
struct foo* const self
) {
// assume foobar_lib_create succeeded...
self->m_bar = foobar_lib_create(...);
// now we must destroy it in foo_destroy after
// the caller logic is done with it.
}
foo_destroy(
struct foo const* const self
) {
foobar_lib_destroy(self->m_bar);
}
__________________________
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-23 13:50 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bghat$25m2f$1@dont-email.me> |
| In reply to | #125232 |
On 10/23/2026 9:57 AM, Peter Flass wrote:
> On 10/23/26 02:45, David Brown wrote:
>> On 23/10/2026 08:25, Lawrence D’Oliveiro wrote:
>>> On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:
>>>
>>>> On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote:
>>>>>
>>>>> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:
>>>>>
>>>>>> That's why I try to use PL/I AUTOMATIC (stack) storage and not
>>>>>> allocate a lot of stuff. You need to have a disciplined approach
>>>>>> if you allocate random stuff here and there.
>>>>>
>>>>> What if you’re building an object that needs to be returned to the
>>>>> caller?
>>>>
>>>> Have the caller have the object before hand and call a function to
>>>> initialize it?
>>>
>>> I’m assuming that all that BASIC programming hasn’t got to your head,
>>> and you’re not serious. ;)
>>
>> Chris' wording is perhaps poor, but the principle is right.
>>
>> I don't know PL/I or Fortran, but in C if you have :
>>
>> typedef struct data_struct { int a; int xs[20]; } S ;
>>
>> S build_some_data(void) {
>> S s;
>>
>> s.a = 123;
>> for (int i = 0; i < 20; i++) s.xs[i] = i;
>>
>> return s;
>> }
>>
>> void foo() {
>> S s = build_some_data();
>> }
>>
>>
>> then it is typically handled as though you had written :
>>
>> void build_some_data(S * p) {
>> p->a = 123;
>> for (int i = 0; i < 20; i++) p->xs[i] = i;
>>
>> return;
>> }
>>
>> void foo() {
>> S s;
>> build_some_data(&s);
>> }
>>
>>
>> That is - the caller creates the /space/ for the returned object, but
>> does not do any kind of initialisation. It passes a pointer to that
>> space as a hidden parameter to the function that wants to return the
>> object.
>>
>> That principle should work fine in any language, as long as the size
>> of the returned object is known by the caller code.
>
> That last sentence is why it would not work fine,
Or have an API that can give us the size of the object the caller needs
to create. So, again pseudo code:
size = foolib_create_get_size(...);
foo_alloc_req fareq = { };
foolib_create_get_alloc_req(&fareq);
foo = create_on_the_stack_etc(size, &fareq);
// The API would have all of that as prerequisites so the caller knows
// about it. Alignment requirements, etc.
foolib_init(foo);
...
foolib_destroy(foo);
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2026-10-24 12:43 +0200 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bi23m$2jjto$2@dont-email.me> |
| In reply to | #125232 |
On 23/10/2026 18:57, Peter Flass wrote:
> On 10/23/26 02:45, David Brown wrote:
>> On 23/10/2026 08:25, Lawrence D’Oliveiro wrote:
>>> On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:
>>>
>>>> On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote:
>>>>>
>>>>> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:
>>>>>
>>>>>> That's why I try to use PL/I AUTOMATIC (stack) storage and not
>>>>>> allocate a lot of stuff. You need to have a disciplined approach
>>>>>> if you allocate random stuff here and there.
>>>>>
>>>>> What if you’re building an object that needs to be returned to the
>>>>> caller?
>>>>
>>>> Have the caller have the object before hand and call a function to
>>>> initialize it?
>>>
>>> I’m assuming that all that BASIC programming hasn’t got to your head,
>>> and you’re not serious. ;)
>>
>> Chris' wording is perhaps poor, but the principle is right.
>>
>> I don't know PL/I or Fortran, but in C if you have :
>>
>> typedef struct data_struct { int a; int xs[20]; } S ;
>>
>> S build_some_data(void) {
>> S s;
>>
>> s.a = 123;
>> for (int i = 0; i < 20; i++) s.xs[i] = i;
>>
>> return s;
>> }
>>
>> void foo() {
>> S s = build_some_data();
>> }
>>
>>
>> then it is typically handled as though you had written :
>>
>> void build_some_data(S * p) {
>> p->a = 123;
>> for (int i = 0; i < 20; i++) p->xs[i] = i;
>>
>> return;
>> }
>>
>> void foo() {
>> S s;
>> build_some_data(&s);
>> }
>>
>>
>> That is - the caller creates the /space/ for the returned object, but
>> does not do any kind of initialisation. It passes a pointer to that
>> space as a hidden parameter to the function that wants to return the
>> object.
>>
>> That principle should work fine in any language, as long as the size
>> of the returned object is known by the caller code.
>
> That last sentence is why it would not work fine,
OK. Knowing the size of the returned object is an absolute requirement
for pre-allocation by the caller, and it is a requirement that is fine
for a lot of situations and a lot of languages. But if it is not the
case for PL/I, Fortran, or any other particular language (or particular
function in any language), then I fully agree - the object's space can't
be handled by the caller.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 19:29 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bp2ac$15h60$1@dont-email.me> |
| In reply to | #125293 |
On 10/24/2026 3:43 AM, David Brown wrote:
> On 23/10/2026 18:57, Peter Flass wrote:
>> On 10/23/26 02:45, David Brown wrote:
>>> On 23/10/2026 08:25, Lawrence D’Oliveiro wrote:
>>>> On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:
>>>>
>>>>> On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote:
>>>>>>
>>>>>> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:
>>>>>>
>>>>>>> That's why I try to use PL/I AUTOMATIC (stack) storage and not
>>>>>>> allocate a lot of stuff. You need to have a disciplined approach
>>>>>>> if you allocate random stuff here and there.
>>>>>>
>>>>>> What if you’re building an object that needs to be returned to the
>>>>>> caller?
>>>>>
>>>>> Have the caller have the object before hand and call a function to
>>>>> initialize it?
>>>>
>>>> I’m assuming that all that BASIC programming hasn’t got to your head,
>>>> and you’re not serious. ;)
>>>
>>> Chris' wording is perhaps poor, but the principle is right.
>>>
>>> I don't know PL/I or Fortran, but in C if you have :
>>>
>>> typedef struct data_struct { int a; int xs[20]; } S ;
>>>
>>> S build_some_data(void) {
>>> S s;
>>>
>>> s.a = 123;
>>> for (int i = 0; i < 20; i++) s.xs[i] = i;
>>>
>>> return s;
>>> }
>>>
>>> void foo() {
>>> S s = build_some_data();
>>> }
>>>
>>>
>>> then it is typically handled as though you had written :
>>>
>>> void build_some_data(S * p) {
>>> p->a = 123;
>>> for (int i = 0; i < 20; i++) p->xs[i] = i;
>>>
>>> return;
>>> }
>>>
>>> void foo() {
>>> S s;
>>> build_some_data(&s);
>>> }
>>>
>>>
>>> That is - the caller creates the /space/ for the returned object, but
>>> does not do any kind of initialisation. It passes a pointer to that
>>> space as a hidden parameter to the function that wants to return the
>>> object.
>>>
>>> That principle should work fine in any language, as long as the size
>>> of the returned object is known by the caller code.
>>
>> That last sentence is why it would not work fine,
>
> OK. Knowing the size of the returned object is an absolute requirement
> for pre-allocation by the caller, and it is a requirement that is fine
> for a lot of situations and a lot of languages. But if it is not the
> case for PL/I, Fortran, or any other particular language (or particular
> function in any language), then I fully agree - the object's space can't
> be handled by the caller.
>
Use when the API provides it, or else, well, read the api learn and know
how to use it. If it allows the caller to make the memory it needs, so
be it, if not, who cares?
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <Peter@Iron-Spring.com> |
|---|---|
| Date | 2026-10-23 09:02 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bg0fa$1unku$1@dont-email.me> |
| In reply to | #125197 |
On 10/22/26 22:29, Chris M. Thomasson wrote: > On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote: >> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote: >> >>> That's why I try to use PL/I AUTOMATIC (stack) storage and not >>> allocate a lot of stuff. You need to have a disciplined approach if >>> you allocate random stuff here and there. >> >> What if you’re building an object that needs to be returned to the >> caller? > > Have the caller have the object before hand and call a function to > initialize it? That obviously wouldn't work, since then the caller would have to know something about the object beforehand. I think you'd have to depend on the compiler to destroy the object when it goes out of scope, unless the caller destroys it itself.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-23 19:19 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bgc00$23hkg$1@dont-email.me> |
| In reply to | #125228 |
On Fri, 23 Oct 2026 09:02:50 -0700, Peter Flass wrote: > On 10/22/26 22:29, Chris M. Thomasson wrote: >> >> On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote: >>> >>> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote: >>> >>>> That's why I try to use PL/I AUTOMATIC (stack) storage and not >>>> allocate a lot of stuff. You need to have a disciplined approach >>>> if you allocate random stuff here and there. >>> >>> What if you’re building an object that needs to be returned to the >>> caller? >> >> Have the caller have the object before hand and call a function to >> initialize it? > > That obviously wouldn't work, since then the caller would have to > know something about the object beforehand. And what if the object didn’t consist of just *one* dynamically-allocated block, but needed links to other blocks as well? What if it needed objects dynamically allocated by other APIs, the details of which are internal to those APIs? Is the caller required to know about all these implementation details? In short, the concept doesn’t scale, because it completely breaks the concept of data abstraction. And it just pushes the dynamic-allocation problem elsewhere, without making it easier.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-23 13:56 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bghmk$25qd0$1@dont-email.me> |
| In reply to | #125239 |
On 10/23/2026 12:19 PM, Lawrence D’Oliveiro wrote:
> On Fri, 23 Oct 2026 09:02:50 -0700, Peter Flass wrote:
>
>> On 10/22/26 22:29, Chris M. Thomasson wrote:
>>>
>>> On 10/22/2026 8:19 PM, Lawrence D’Oliveiro wrote:
>>>>
>>>> On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:
>>>>
>>>>> That's why I try to use PL/I AUTOMATIC (stack) storage and not
>>>>> allocate a lot of stuff. You need to have a disciplined approach
>>>>> if you allocate random stuff here and there.
>>>>
>>>> What if you’re building an object that needs to be returned to the
>>>> caller?
>>>
>>> Have the caller have the object before hand and call a function to
>>> initialize it?
>>
>> That obviously wouldn't work, since then the caller would have to
>> know something about the object beforehand.
>
> And what if the object didn’t consist of just *one*
> dynamically-allocated block, but needed links to other blocks as well?
> What if it needed objects dynamically allocated by other APIs, the
> details of which are internal to those APIs? Is the caller required to
> know about all these implementation details?
>
> In short, the concept doesn’t scale, because it completely breaks the
> concept of data abstraction.
>
> And it just pushes the dynamic-allocation problem elsewhere, without
> making it easier.
It can be made to work, and if it fits in with your "scheme", okay, if
not so what? Have an API that can give us the size of the object the
caller needs to create. So, again pseudo code:
size = foolib_create_get_size(...);
foo_alloc_req fareq = { };
foolib_create_get_alloc_req(&fareq);
foo = create_on_the_stack_etc(size, &fareq);
// The API would have all of that as prerequisites so the caller knows
// about it. Alignment requirements, etc.
foolib_init(foo);
...
foolib_destroy(foo);
The caller can gain the size, and the alignment requirements up front.
It can allocate it using any of its means. Then use that to call into
the lib. It works.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-23 22:42 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bgnsc$27pn2$2@dont-email.me> |
| In reply to | #125260 |
On Fri, 23 Oct 2026 13:56:49 -0700, Chris M. Thomasson wrote: > On 10/23/2026 12:19 PM, Lawrence D’Oliveiro wrote: >> >> In short, the concept doesn’t scale, because it completely breaks >> the concept of data abstraction. >> >> And it just pushes the dynamic-allocation problem elsewhere, >> without making it easier. > > It can be made to work ... I’m sure it’s *possible*, but what is the *point*? The whole aim of levels of abstraction is to tame the multi-headed beast of complexity that is computer programming. What you are doing here is breaking down those levels, all in the aid of, I don’t know, just to keep using gotos in your code, or something.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-23 17:01 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bgsgo$299in$4@dont-email.me> |
| In reply to | #125269 |
On 10/23/2026 3:42 PM, Lawrence D’Oliveiro wrote: > On Fri, 23 Oct 2026 13:56:49 -0700, Chris M. Thomasson wrote: > >> On 10/23/2026 12:19 PM, Lawrence D’Oliveiro wrote: >>> >>> In short, the concept doesn’t scale, because it completely breaks >>> the concept of data abstraction. >>> >>> And it just pushes the dynamic-allocation problem elsewhere, >>> without making it easier. >> >> It can be made to work ... > > I’m sure it’s *possible*, but what is the *point*? > > The whole aim of levels of abstraction is to tame the multi-headed > beast of complexity that is computer programming. What you are doing > here is breaking down those levels, all in the aid of, I don’t know, > just to keep using gotos in your code, or something. Well, not about goto's and such. Just so a lib can inform the caller as to what it needs to work with. The caller sets it up, then calls into the init etc. Its being used in a lot of places. Take Vulkan.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-24 03:33 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bh8ue$2coe1$1@dont-email.me> |
| In reply to | #125280 |
On Fri, 23 Oct 2026 17:01:28 -0700, Chris M. Thomasson wrote: > On 10/23/2026 3:42 PM, Lawrence D’Oliveiro wrote: >> >> On Fri, 23 Oct 2026 13:56:49 -0700, Chris M. Thomasson wrote: >> >>> On 10/23/2026 12:19 PM, Lawrence D’Oliveiro wrote: >>>> >>>> In short, the concept doesn’t scale, because it completely breaks >>>> the concept of data abstraction. >>>> >>>> And it just pushes the dynamic-allocation problem elsewhere, >>>> without making it easier. >>> >>> It can be made to work ... >> >> I’m sure it’s *possible*, but what is the *point*? >> >> The whole aim of levels of abstraction is to tame the multi-headed >> beast of complexity that is computer programming. What you are >> doing here is breaking down those levels, all in the aid of, I >> don’t know, just to keep using gotos in your code, or something. > > Well, not about goto's and such. Just so a lib can inform the caller > as to what it needs to work with. The caller sets it up, then calls > into the init etc. Its being used in a lot of places. Take Vulkan. Where in Vulkan? Exposing implementation details to the caller not only increases complexity, it also limits the implementor’s ability to change those details later.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-24 13:26 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bj493$31thn$1@dont-email.me> |
| In reply to | #125284 |
On 10/23/2026 8:33 PM, Lawrence D’Oliveiro wrote: > On Fri, 23 Oct 2026 17:01:28 -0700, Chris M. Thomasson wrote: > >> On 10/23/2026 3:42 PM, Lawrence D’Oliveiro wrote: >>> >>> On Fri, 23 Oct 2026 13:56:49 -0700, Chris M. Thomasson wrote: >>> >>>> On 10/23/2026 12:19 PM, Lawrence D’Oliveiro wrote: >>>>> >>>>> In short, the concept doesn’t scale, because it completely breaks >>>>> the concept of data abstraction. >>>>> >>>>> And it just pushes the dynamic-allocation problem elsewhere, >>>>> without making it easier. >>>> >>>> It can be made to work ... >>> >>> I’m sure it’s *possible*, but what is the *point*? >>> >>> The whole aim of levels of abstraction is to tame the multi-headed >>> beast of complexity that is computer programming. What you are >>> doing here is breaking down those levels, all in the aid of, I >>> don’t know, just to keep using gotos in your code, or something. >> >> Well, not about goto's and such. Just so a lib can inform the caller >> as to what it needs to work with. The caller sets it up, then calls >> into the init etc. Its being used in a lot of places. Take Vulkan. > > Where in Vulkan? Exposing implementation details to the caller not > only increases complexity, it also limits the implementor’s ability to > change those details later. Iiic, vkGetBufferMemoryRequirements and vkGetImageMemoryRequirements, which return a VkMemoryRequirements struct containing size, alignment, and memoryTypeBits. The caller allocates the memory with vkAllocateMemory and binds it with vkBindBufferMemory. Also, iirc io_uring: IORING_SETUP_NO_MMAP (Linux 6.5+) lets the caller supply the memory for the rings and SQE array. It must be suitably aligned (page or huge page), and the caller has to compute how big it needs to be from the entry count and flags. So it can be made to work.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-24 13:27 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bj4bj$31thn$2@dont-email.me> |
| In reply to | #125310 |
On 10/24/2026 1:26 PM, Chris M. Thomasson wrote: > Iiic, vkGetBufferMemoryRequirements and vkGetImageMemoryRequirements, > which return a VkMemoryRequirements struct containing size, alignment, > and memoryTypeBits. The caller allocates the memory with > vkAllocateMemory and binds it with vkBindBufferMemory. > > Also, iirc io_uring: IORING_SETUP_NO_MMAP (Linux 6.5+) lets the caller > supply the memory for the rings and SQE array. It must be suitably > aligned (page or huge page), and the caller has to compute how big it > needs to be from the entry count and flags. > > So it can be made to work. Or what about miniaudio’s ma_engine_get_heap_size plus ma_engine_init_preallocated
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-24 22:32 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bjblp$340l8$7@dont-email.me> |
| In reply to | #125311 |
On Sat, 24 Oct 2026 13:27:30 -0700, Chris M. Thomasson wrote: > Or what about miniaudio’s ma_engine_get_heap_size plus > ma_engine_init_preallocated No idea about that, but the same principle would apply.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 19:57 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bp3uj$15rmq$2@dont-email.me> |
| In reply to | #125317 |
On 10/24/2026 3:32 PM, Lawrence D’Oliveiro wrote: > On Sat, 24 Oct 2026 13:27:30 -0700, Chris M. Thomasson wrote: > >> Or what about miniaudio’s ma_engine_get_heap_size plus >> ma_engine_init_preallocated > > No idea about that, but the same principle would apply. You sound like you never worked with any of it before?????
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 20:09 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bp4m0$164bs$1@dont-email.me> |
| In reply to | #125317 |
On 10/24/2026 3:32 PM, Lawrence D’Oliveiro wrote: > On Sat, 24 Oct 2026 13:27:30 -0700, Chris M. Thomasson wrote: > >> Or what about miniaudio’s ma_engine_get_heap_size plus >> ma_engine_init_preallocated > > No idea about that, but the same principle would apply. Sure you do, or what are you writing about anyway? Really? You seem like the oracle, right?
[toc] | [prev] | [next] | [standalone]
Page 23 of 27 — ← Prev page 1 … 21 22 [23] 24 25 … 27 Next page →
Back to top | Article view | comp.lang.c++
csiph-web