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 25 of 27 — ← Prev page 1 … 23 24 [25] 26 27 Next page →
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-11-04 02:48 -0800 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11cf2hi$irnr$8@dont-email.me> |
| In reply to | #125453 |
On 10/27/2026 11:36 AM, Scott Lurndal wrote: > Peter Flass <Peter@Iron-Spring.com> writes: >> On 10/27/26 08:00, James Kuyper wrote: >>> On 2026-10-26 17:45, Lawrence D’Oliveiro wrote: >>>> On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote: >>> [restore snippage]>> On 2026-10-25 23:39, Lawrence D’Oliveiro wrote: >>>>>> On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote: >>>>>> >>>>>>> A caller provided buffer is normal with a lot of API's out there. >>>>>> >>>>>> No it isn’t. It’s not a good way to manage things, anyway: instead of >>>>>> solving the resource-allocation problem once and for all in the >>>>>> library API, you are pushing the burden onto all the client code, each >>>>>> one of which has to solve it for itself. >>>>>> >>>>>> That’s a dumb way to design things. >>> >>>>> HUH? How do you call say, fread without a user provided buffer? >>>> >>>> Relevance being? >>> >>> fread() uses a caller-provided buffer, which, according to your previous >>> comment, "push[es] the burden onto all the client code, each one of >>> which has to solve it for itself", so according to you, "That's a dumb >>> way to design things"..If that isn't your actual opinion of fread(), >>> your comments need to be at least a little more nuanced to avoid >>> applying to fread(). >> >> The difference is that the size of the buffer for fread() is the maximum >> you want/expect to read. The size of an object is the size it is, not >> necessarily what you expect. If you don't provide enough space you will >> truncate. > > Which isn't a significant issue with fread, since the underlying stdio > buffer (or kernel file cache or terminal driver buffer) will hold the > unread information for the next call to fread. > > fread(3) is basically obsolete for most high-performance applications > which map the file directly into the process address space (mmap). Ditto.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-27 22:22 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11br86k$1uehc$2@dont-email.me> |
| In reply to | #125450 |
On Tue, 27 Oct 2026 11:00:08 -0400, James Kuyper wrote: > On 2026-10-26 17:45, Lawrence D’Oliveiro wrote: >> >> On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote: >>> >>> On 2026-10-25 23:39, Lawrence D’Oliveiro wrote: >>>> >>>> On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote: >>>> >>>>> A caller provided buffer is normal with a lot of API's out there. >>>> >>>> No it isn’t. It’s not a good way to manage things, anyway: >>>> instead of solving the resource-allocation problem once and for >>>> all in the library API, you are pushing the burden onto all the >>>> client code, each one of which has to solve it for itself. >>>> >>>> That’s a dumb way to design things. > >>> HUH? How do you call say, fread without a user provided buffer? >> >> Relevance being? > > fread() uses a caller-provided buffer, which, according to your previous > comment, "push[es] the burden onto all the client code, each one of > which has to solve it for itself", so according to you, "That's a dumb > way to design things".. Not even paying attention to what’s being said in the parts you quoted, never mind the parts you didn’t. Note my remark above about “solving the resource allocation problem”; elsewhere I asked: “What if you’re building an object that needs to be returned to the caller?” Not clear yet what we’re talking about here? We’re not talking about random API calls, we’re talking about libraries that need to create and manage abstract objects that encapsulate the function they are providing!
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@alumni.caltech.edu> |
|---|---|
| Date | 2026-10-27 21:35 -0400 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11brjgd$21rhi$1@dont-email.me> |
| In reply to | #125456 |
Thanks to my killfile, I don't see messages posted by Chris M. Thomasson, just other people's responses to them. > On 2026-10-25 20:42, Lawrence D’Oliveiro wrote: >> On Sun, 25 Oct 2026 16:16:26 -0700, Chris M. Thomasson wrote: >> >>> Even analogous, to say, an API that says read n bytes and store into >>> buffer. Well, the caller has lifetime of said buffer. The caller makes >>> the buffer, calls into the function. >> >> So how is the caller supposed to manage that memory? That's the oldest message I can find on this sub-thread, and also the very last message I can find preceding the one quoted below, and it's clearly describing an fread()-like interface, not a function that returns objects of sizes unknown to the caller. If the messages I don't see gave some other context to this sub-thread, I had no way of knowing about it. On 2026-10-27 18:22, Lawrence D’Oliveiro wrote: > On Tue, 27 Oct 2026 11:00:08 -0400, James Kuyper wrote: > >> On 2026-10-26 17:45, Lawrence D’Oliveiro wrote: >>> >>> On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote: >>>> >>>> On 2026-10-25 23:39, Lawrence D’Oliveiro wrote: >>>>> >>>>> On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote: >>>>> >>>>>> A caller provided buffer is normal with a lot of API's out there. >>>>> >>>>> No it isn’t. It’s not a good way to manage things, anyway: >>>>> instead of solving the resource-allocation problem once and for >>>>> all in the library API, you are pushing the burden onto all the >>>>> client code, each one of which has to solve it for itself. >>>>> >>>>> That’s a dumb way to design things. >> >>>> HUH? How do you call say, fread without a user provided buffer? >>> >>> Relevance being? >> >> fread() uses a caller-provided buffer, which, according to your previous >> comment, "push[es] the burden onto all the client code, each one of >> which has to solve it for itself", so according to you, "That's a dumb >> way to design things".. > > Not even paying attention to what’s being said in the parts you > quoted, never mind the parts you didn’t. Note my remark above about > “solving the resource allocation problem”; elsewhere I asked: “What if > you’re building an object that needs to be returned to the caller?” Yes, and without the context that applies elsewhere, your comment about resource allocation comes off as a non-sequitur. > Not clear yet what we’re talking about here? We’re not talking about > random API calls, we’re talking about libraries that need to create > and manage abstract objects that encapsulate the function they are > providing! I can find no mention of that topic anywhere on this sub-thread. It might be in the parts of Chris's messages that I didn't see and you didn't quote.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-28 01:43 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11brk0r$21r0v$2@dont-email.me> |
| In reply to | #125457 |
On Tue, 27 Oct 2026 21:35:09 -0400, James Kuyper wrote:
> ... without the context that applies elsewhere, your comment about
> resource allocation comes off as a non-sequitur.
That’s just an excuse. Other comments of mine, from further back in
this particular line of this thread:
* “What if you’re building an object that needs to be returned to the
caller?”
* “The principle applies to Fortran as it does to any language where
you have to explicitly manage storage allocations.”
* “If you have to do cleanup at each level before exiting, then it works
perfectly well.”
Did you notice any of that?
From elsewhere in the discussion:
I find the C code I write tends to do a lot of dynamic resource
allocations. These can sometimes fail with errors. So error
recovery will invariably involve cleaning up those parts of the
allocations which already succeeded. Gotos are no good for this;
you need to exit levels of structure nesting one by one, disposing
of allocations as you go.
I put together an example here
<https://gitlab.com/ldo/a_structured_discipline_of_programming>.
This is an extension module that offers services to Python code,
because that is just about the worst example I could think of, for
those who think gotos can cut it.
Did you pay attention to any of that?
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@alumni.caltech.edu> |
|---|---|
| Date | 2026-10-27 22:18 -0400 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11brm2g$22hpk$1@dont-email.me> |
| In reply to | #125458 |
On 2026-10-27 21:43, Lawrence D’Oliveiro wrote: > On Tue, 27 Oct 2026 21:35:09 -0400, James Kuyper wrote: > >> ... without the context that applies elsewhere, your comment about >> resource allocation comes off as a non-sequitur. > > That’s just an excuse. Other comments of mine, from further back in > this particular line of this thread: > > * “What if you’re building an object that needs to be returned to the > caller?” > * “The principle applies to Fortran as it does to any language where > you have to explicitly manage storage allocations.” > * “If you have to do cleanup at each level before exiting, then it works > perfectly well.” > > Did you notice any of that? No, none of those comments appear anywhere in this sub-thread as displayed by Thunderbird. How do they fit in to the sequence of messages that lead to this one? If they appeared in some other sub-thread, that's not relevant; the fact that something is being discussed in another sub-thread doesn't make it relevant to what's being discussed in this one. However, if those comments occur in Chris' text that I never saw, or in messages on this sub-thread that are prior to the earliest one I quoted, then they would be relevant. The references for the oldest message I quoted indicate that there were 20 previous ones in that sub-thread, but they don't display as predecessors of that message. This is a common problem when I filter out all the messages posted by someone. If that person is a significant contributor to a particular thread, that thread gets chopped up into pieces and Thunderbird fails to notice that those pieces are related to each other.
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <Peter@Iron-Spring.com> |
|---|---|
| Date | 2026-10-27 19:28 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11brmkv$22lhe$1@dont-email.me> |
| In reply to | #125458 |
On 10/27/26 18:43, Lawrence D’Oliveiro wrote: > On Tue, 27 Oct 2026 21:35:09 -0400, James Kuyper wrote: > >> ... without the context that applies elsewhere, your comment about >> resource allocation comes off as a non-sequitur. > > That’s just an excuse. Other comments of mine, from further back in > this particular line of this thread: > > * “What if you’re building an object that needs to be returned to the > caller?” > * “The principle applies to Fortran as it does to any language where > you have to explicitly manage storage allocations.” > * “If you have to do cleanup at each level before exiting, then it works > perfectly well.” > > Did you notice any of that? > > From elsewhere in the discussion: > > I find the C code I write tends to do a lot of dynamic resource > allocations. These can sometimes fail with errors. So error > recovery will invariably involve cleaning up those parts of the > allocations which already succeeded. Gotos are no good for this; > you need to exit levels of structure nesting one by one, disposing > of allocations as you go. > > I put together an example here > <https://gitlab.com/ldo/a_structured_discipline_of_programming>. > This is an extension module that offers services to Python code, > because that is just about the worst example I could think of, for > those who think gotos can cut it. > > Did you pay attention to any of that? You could keep track of the allocations in a list (or whatever) and then walk thru and clean them up at once.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-28 14:16 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11btont$2q523$1@dont-email.me> |
| In reply to | #125458 |
On 10/27/2026 6:43 PM, Lawrence D’Oliveiro wrote: > On Tue, 27 Oct 2026 21:35:09 -0400, James Kuyper wrote: > >> ... without the context that applies elsewhere, your comment about >> resource allocation comes off as a non-sequitur. > > That’s just an excuse. Other comments of mine, from further back in > this particular line of this thread: > > * “What if you’re building an object that needs to be returned to the > caller?” > * “The principle applies to Fortran as it does to any language where > you have to explicitly manage storage allocations.” > * “If you have to do cleanup at each level before exiting, then it works > perfectly well.” > > Did you notice any of that? > > From elsewhere in the discussion: > > I find the C code I write tends to do a lot of dynamic resource > allocations. These can sometimes fail with errors. So error > recovery will invariably involve cleaning up those parts of the > allocations which already succeeded. Gotos are no good for this; > you need to exit levels of structure nesting one by one, disposing > of allocations as you go. > > I put together an example here > <https://gitlab.com/ldo/a_structured_discipline_of_programming>. > This is an extension module that offers services to Python code, > because that is just about the worst example I could think of, for > those who think gotos can cut it. > > Did you pay attention to any of that? Its actually pretty simple. There are libs out there that allow the caller to create the memory it needs. io_uring is just one of them. DirectX12 is another. The user creates all the memory, aligns it, etc, and can update a single frame with a single memcpy.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-11-01 23:38 +0000 |
| Subject | Re: Structured Programming (was Re: “The end of software secrecy is almost upon us”) |
| Message-ID | <11c8ihn$2dr35$2@dont-email.me> |
| In reply to | #125458 |
Anyway, to get the discussion back on track:
I put together an example here
<https://gitlab.com/ldo/a_structured_discipline_of_programming>. This
is an extension module that offers services to Python code, because
that is just about the worst example I could think of, for those who
think gotos can cut it.
Problems I am trying to address:
* Leaking memory: allocating something and forgetting to dispose of
it
* Double-free: the opposite problem, trying to free a memory block
that has already been freed
The basic structured-programming pattern I follow is:
1: Initialize a pointer variable to `NULL`
2: Allocate memory for the pointer (this might fail)
3: Correctly free the pointer memory, regardless of allocation
success/failure
This project uses the implementation of a Python extension module as a
specific example, since Python itself is a highly dynamic language,
and so code that is written in a lower-level-language like C for
interfacing to Python typically has to deal a lot with allocation and
management of Python objects and other dynamic memory.
In more concrete terms, the code pattern looks like this:
PyObject * obj = NULL; /* step 1 */
do /*once*/
{
... possible other stuff ...
allocate obj; /* step 2 */
if (PyErr_Occurred())
break;
... possible other stuff using obj ...
}
while (false);
Py_XDECREF(obj); /* step 3 */
Assuming there are no `goto`s in the “...” parts (or `return`
statements, or shenanigans like `setjmp`(3)/`longjmp`(3)), it should
be clear that, regardless of what happens in those parts (provided
they don’t free or reallocate `obj`), any memory allocated to `obj`
will be correctly freed.
Key to this pattern is the fact that `Py_XDECREF` is a noop (and
raises no error) if it is passed a `NULL` pointer. This is also the
semantics of the `free`(3) routine in the C standard library, and I
recommend that any memory-disposal routine you create implement the
same behaviour. It saves checking for unallocated storage in the
cleanup code: just unconditionally dispose of everything temporary
that might have been allocated.
The above basic structure scales easily. For example, coping with
multiple objects needing allocating:
PyObject * obj1 = NULL;
PyObject * obj2 = NULL;
do /*once*/
{
... possible other stuff ...
allocate obj1;
if (PyErr_Occurred())
break;
... possible other stuff using obj1 ...
allocate obj2;
if (PyErr_Occurred())
break;
... possible other stuff using obj1 and obj2 ...
}
while (false);
Py_XDECREF(obj1);
Py_XDECREF(obj2);
Nested blocks:
PyObject * obj1 = NULL;
do /*once*/
{
... possible other stuff ...
allocate obj1;
if (PyErr_Occurred())
break;
... possible other stuff using obj1 ...
{
PyObject * obj2 = NULL;
do /*once*/
{
... even more possible stuff using obj1 ...
allocate obj2;
if (PyErr_Occurred())
break;
... possible other stuff using obj1 and obj2 ...
}
while (false);
Py_XDECREF(obj2);
}
if (PyErr_Occurred())
break;
... yet more possible stuff using obj1 ...
}
while (false);
Py_XDECREF(obj1);
Allocation within loops:
for (ssize_t i = 0;;)
{
if (i == nr_items)
break;
PyObject * const item = PyTuple_GetItem(items, i);
if (item == NULL)
break;
{
PyObject * key = NULL;
PyObject * value = NULL;
do /*once*/
{
... construct key ...
if (PyErr_Occurred())
break;
... construct value ...
if (PyErr_Occurred())
break;
if (PyDict_SetItem(tempresult, key, value) < 0)
break;
}
while (false);
Py_XDECREF(key);
Py_XDECREF(value);
}
if (PyErr_Occurred())
break;
++i;
} /*for*/
if (PyErr_Occurred())
break;
Etc, etc.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-25 19:21 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bmdee$5qol$1@dont-email.me> |
| In reply to | #125372 |
On 10/25/2026 5:42 PM, Lawrence D’Oliveiro wrote: > On Sun, 25 Oct 2026 16:16:26 -0700, Chris M. Thomasson wrote: > >> Even analogous, to say, an API that says read n bytes and store into >> buffer. Well, the caller has lifetime of said buffer. The caller makes >> the buffer, calls into the function. > > So how is the caller supposed to manage that memory? Managing the memory is the caller’s job in C anyway. That’s the trade-off the language makes. read, recv, and mmap all work this way. This just applies the same contract to the lib’s own object.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-26 03:40 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bmi37$78mo$2@dont-email.me> |
| In reply to | #125376 |
On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote: > Managing the memory is the caller’s job in C anyway. Does that apply to the caller of library APIs like malloc(3) and free(3)?
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 13:29 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bod6h$ugib$3@dont-email.me> |
| In reply to | #125381 |
On 10/25/2026 8:40 PM, Lawrence D’Oliveiro wrote: > On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote: > >> Managing the memory is the caller’s job in C anyway. > > Does that apply to the caller of library APIs like malloc(3) and > free(3)? Yes. The caller calls malloc, if it succeeded, the caller needs to free what it got... Right?
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 13:33 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bodf4$unqs$1@dont-email.me> |
| In reply to | #125417 |
On 10/26/2026 1:29 PM, Chris M. Thomasson wrote: > On 10/25/2026 8:40 PM, Lawrence D’Oliveiro wrote: >> On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote: >> >>> Managing the memory is the caller’s job in C anyway. >> >> Does that apply to the caller of library APIs like malloc(3) and >> free(3)? > > Yes. The caller calls malloc, if it succeeded, the caller needs to free > what it got... Right? Say a lib that has foo_create... Well, the damn called must remember to call foo_destroy, right?
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-26 21:45 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bohlf$10aqu$1@dont-email.me> |
| In reply to | #125418 |
On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote: > Say a lib that has foo_create... Well, the damn called must remember > to call foo_destroy, right? Are you backpedalling from your previous idea that the caller must allocate the memory for the library to use?
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 14:53 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11boi5d$107r1$5@dont-email.me> |
| In reply to | #125422 |
On 10/26/2026 2:45 PM, Lawrence D’Oliveiro wrote: > On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote: > >> Say a lib that has foo_create... Well, the damn called must remember >> to call foo_destroy, right? > > Are you backpedalling from your previous idea that the caller must > allocate the memory for the library to use? Where did I say must? I said some libs allow the caller to create their internal state. You are the one that seems to not understand it? Either way, the caller needs to manage things in C. malloc/free, etc.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-26 22:20 +0000 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bojn7$10aqu$10@dont-email.me> |
| In reply to | #125427 |
On Mon, 26 Oct 2026 14:53:48 -0700, Chris M. Thomasson wrote: > On 10/26/2026 2:45 PM, Lawrence D’Oliveiro wrote: >> >> On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote: >> >>> Say a lib that has foo_create... Well, the damn called must >>> remember to call foo_destroy, right? >> >> Are you backpedalling from your previous idea that the caller must >> allocate the memory for the library to use? > > Where did I say must? You said “Managing the memory is the caller’s job in C anyway.” You didn’t say “could be the caller’s job” as in “the caller could have a choice”, you said “*is* the caller’s job”. No choice. I.e. the caller *must* manage memory.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 15:42 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bol0q$11j3t$1@dont-email.me> |
| In reply to | #125431 |
On 10/26/2026 3:20 PM, Lawrence D’Oliveiro wrote: > On Mon, 26 Oct 2026 14:53:48 -0700, Chris M. Thomasson wrote: > >> On 10/26/2026 2:45 PM, Lawrence D’Oliveiro wrote: >>> >>> On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote: >>> >>>> Say a lib that has foo_create... Well, the damn called must >>>> remember to call foo_destroy, right? >>> >>> Are you backpedalling from your previous idea that the caller must >>> allocate the memory for the library to use? >> >> Where did I say must? > > You said “Managing the memory is the caller’s job in C anyway.” You > didn’t say “could be the caller’s job” as in “the caller could have a > choice”, you said “*is* the caller’s job”. No choice. I.e. the caller > *must* manage memory. But, the caller must take care in C. Say a lib that allows the caller to create their own memory from the requirements reaped from the lib. Okay. Fine. Also, take a lib that is more "encapsulated" than say a pure foo_create/destroy. The caller must remember to call foo_destroy, right? Using io_uring is a fun one. The caller created the memory, iirc from mmap, so the kernel can use it. The Kernel punts off the lifetime management of the users ring buffers. The C must manage things regardless. say malloc and free?
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 16:06 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bomd5$1224g$1@dont-email.me> |
| In reply to | #125431 |
On 10/26/2026 3:20 PM, Lawrence D’Oliveiro wrote:
> On Mon, 26 Oct 2026 14:53:48 -0700, Chris M. Thomasson wrote:
>
>> On 10/26/2026 2:45 PM, Lawrence D’Oliveiro wrote:
>>>
>>> On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote:
>>>
>>>> Say a lib that has foo_create... Well, the damn called must
>>>> remember to call foo_destroy, right?
>>>
>>> Are you backpedalling from your previous idea that the caller must
>>> allocate the memory for the library to use?
>>
>> Where did I say must?
>
> You said “Managing the memory is the caller’s job in C anyway.” You
> didn’t say “could be the caller’s job” as in “the caller could have a
> choice”, you said “*is* the caller’s job”. No choice. I.e. the caller
> *must* manage memory.
A simple pattern... Now, some libs can do it others are simply not
designed that way.
foo_alloc_req r = foo_query_alloc(&cfg);
void *mem = aligned_alloc(r.align, r.size); /* once */
for (int i = 0; i < n_jobs; ++i) {
foo *f = foo_init(mem, r.size, &cfg); /* build in the same
block */
/* ... use f ... */
foo_deinit(f); /* object ends, block
stays ours */
}
free(mem); /* once, at the very end */
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2026-10-26 22:29 +0100 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bogni$vva5$1@dont-email.me> |
| In reply to | #125417 |
On 26/10/2026 21:29, Chris M. Thomasson wrote: > On 10/25/2026 8:40 PM, Lawrence D’Oliveiro wrote: >> On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote: >> >>> Managing the memory is the caller’s job in C anyway. >> >> Does that apply to the caller of library APIs like malloc(3) and >> free(3)? > > Yes. The caller calls malloc, if it succeeded, the caller needs to free > what it got... Right? Exactly. The caller is responsible for /managing/ the memory (or it can pass on that responsibility to something else). malloc and free are provide and dispose of memory, they do not manage it.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 14:58 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11boiee$10l23$1@dont-email.me> |
| In reply to | #125421 |
On 10/26/2026 2:29 PM, David Brown wrote: > On 26/10/2026 21:29, Chris M. Thomasson wrote: >> On 10/25/2026 8:40 PM, Lawrence D’Oliveiro wrote: >>> On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote: >>> >>>> Managing the memory is the caller’s job in C anyway. >>> >>> Does that apply to the caller of library APIs like malloc(3) and >>> free(3)? >> >> Yes. The caller calls malloc, if it succeeded, the caller needs to >> free what it got... Right? > > Exactly. The caller is responsible for /managing/ the memory (or it can > pass on that responsibility to something else). malloc and free are > provide and dispose of memory, they do not manage it. > Right. For instance take my ralloc thing. A user can create a big pile of memory, have rallocex carve it up for them (align, etc), and use it. But, the user needs to know how to free that memory. If its on the stack, well, easy. If not call free, or whatever it needs. ralloc does not give a crap where the memory came from.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2026-10-26 15:46 -0700 |
| Subject | Re: “The end of software secrecy is almost upon |
| Message-ID | <11bol7d$11j3t$2@dont-email.me> |
| In reply to | #125381 |
On 10/25/2026 8:40 PM, Lawrence D’Oliveiro wrote: > On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote: > >> Managing the memory is the caller’s job in C anyway. > > Does that apply to the caller of library APIs like malloc(3) and > free(3)? you should print that out and frame it.
[toc] | [prev] | [next] | [standalone]
Page 25 of 27 — ← Prev page 1 … 23 24 [25] 26 27 Next page →
Back to top | Article view | comp.lang.c++
csiph-web