On Fri, 23 Oct 2026 16:22:06 +0800
Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> gabbled:
On 10/23/2026 4:14 PM, boltar@caprica.universe wrote:
In Windows the graphics system just starts up. On the unix X windows
system
initial startup requires a server IP address with optional screen
number then
doing a network connect. Also I don't know the win32 graphics
subsystem but
I suspect it differs fundamentally from the X Windows model so I have
no idea
how you'd square that circle unless the only API you provide is for
top level
GUI components as per libraries such as Gtk and Qt.
The point I was trying to make was that in 1997, when the C++ standard
got finalized, IUP,
-a https://iup.sf.net/
Had a look, requires Lua. No thanks.
On 22/10/2026 22:25, James Kuyper wrote:
On 2026-10-22 12:02, Scott Lurndal wrote:The term in both the C and C++ standards is "abstract machine", but I
The C/C++ "Virtual Machine Model" as described in the language
specifications is an apple.
think it was quite obvious that this is Dan meant when he wrote "virtual machine". ...
On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bd7tj$rh4f$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>>
Most of us have a CS degree. But then we go out into the real world, get a >>> job and find out what real programming on real products entails, not a load >>> of virtual academic naval gazing.
That's because it's not a trade school degree. It's not there to teach
you to program, it's there to teach you the fundamentals that you need to
properly understand programming.
No, it teaches you fundamentals of certain aspects of computer paradigms such as databases, graphics, AI. Most people into computers learn actual programming
long before they hit university.
Engineering schools are even more that way. They don't teach you much
engineering, but they give you all the background that you need to learn
engineering.
Programming isn't pure engineering - its a combination of engineering, logic, art and a trade.
If you just want a job, getting one of these degrees is not for you. It's >> not there for that.
Bill Gates never earned a degree. He seemed to do ok.
On 10/23/26 01:01, boltar@caprica.universe wrote:
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
On Fri, 23 Oct 2026 11:42:38 +0300
Michael S <already5chosen@yahoo.com> gabbled:
On Fri, 23 Oct 2026 08:05:13 -0000 (UTC)
boltar@caprica.universe wrote:
On Thu, 22 Oct 2026 22:48:29 +0300
Michael S <already5chosen@yahoo.com> gabbled:
On Thu, 22 Oct 2026 14:51:31 -0000 (UTC)
boltar@battlestar.co.uk wrote:
I agree that the work for a CS degree is useful. If nothing else
I understand more now.
Most of us have a CS degree.
I don't have it.
How do you know about most?
Oh I dunno, maybe 30 years in the industry working with probably
hundreds of different programmers.
My experience in industry beats yours by few years.
And my statistics differ - CS graduates are not majority of computer
programmers. At best, they are plurality.
Regardless, the point was not industry, but audience of five particular
newsgroups.
Well, the majority of people in programming have some kind of STEM degree, not necessarily CS. For example if you can do electronic engineering or advance maths then programming concepts probably arn't going to be a big deal for you though I have seen plenty of code written by engineers and while it works it tends to be messy. More a case of get the job done fast so we can get on with the real work rather than create something efficient and maintainable.
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Considering how much of my career I've spent working around poor
design decisions and outright bugs in Windows, I'd say that is
self-evident.
Bill Gates never earned a degree. He seemed to do ok.
AFAIK you can't pin that one on him; the Tandy Model 100 was the last
product he actually wrote code for, and that came out in '83, right at
the beginning of development on Windows 1.0. Dunno that he did much on >MS-DOS, either, as the core of that was Tim Paterson's work in, erm, >"adapating" the design of CP/M to the 8086.
On 10/23/2026 5:18 AM, boltar@caprica.universe wrote:
On Fri, 23 Oct 2026 11:42:38 +0300
Michael S <already5chosen@yahoo.com> gabbled:
On Fri, 23 Oct 2026 08:05:13 -0000 (UTC)
boltar@caprica.universe wrote:
On Thu, 22 Oct 2026 22:48:29 +0300
Michael S <already5chosen@yahoo.com> gabbled:
On Thu, 22 Oct 2026 14:51:31 -0000 (UTC)
boltar@battlestar.co.uk wrote:
I agree that the work for a CS degree is useful. If nothing else >>>>>>> I understand more now.
Most of us have a CS degree.
I don't have it.
How do you know about most?
Oh I dunno, maybe 30 years in the industry working with probably
hundreds of different programmers.
My experience in industry beats yours by few years.
And my statistics differ - CS graduates are not majority of computer
programmers. At best, they are plurality.
Regardless, the point was not industry, but audience of five particular
newsgroups.
Well, the majority of people in programming have some kind of STEM degree, >> not necessarily CS. For example if you can do electronic engineering or
advance maths then programming concepts probably arn't going to be a big deal
for you though I have seen plenty of code written by engineers and while it >> works it tends to be messy. More a case of get the job done fast so we can >> get on with the real work rather than create something efficient and
maintainable.
I have a degree in Biochemistry, and spent 5 year in a medical research
lab being professionally unpleasant to rats before switch careers to >software.
It helped that at that time (early 80s) almost no one had a CS degree.
He continued doing code reviews well into the Win 7 era, and a lot of
people wound up having to clean up after him. He was always very
hands-on. I remember in 1978 him being the third tier tech support
hotline for MBASIC bugs. He was incredibly rude.
On 10/23/26 01:01, boltar@caprica.universe wrote:
On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bd7tj$rh4f$1@dont-email.me>,-a <boltar@battlestar.co.uk>
wrote:
Most of us have a CS degree. But then we go out into the real world,
get a
job and find out what real programming on real products entails, not
a load
of virtual academic naval gazing.
That's because it's not a trade school degree.-a It's not there to teach >>> you to program, it's there to teach you the fundamentals that you
need to
properly understand programming.
No, it teaches you fundamentals of certain aspects of computer
paradigms such
as databases, graphics, AI. Most people into computers learn actual
programming
long before they hit university.
Engineering schools are even more that way.-a They don't teach you much
engineering, but they give you all the background that you need to learn >>> engineering.
Programming isn't pure engineering - its a combination of engineering,
logic,
art and a trade.
If you just want a job, getting one of these degrees is not for you.
It's
not there for that.
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads >>> in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but not a process library. Its perfectly possible to simulate a multiprocess enviroment. How do you think pure software versions of virtual machines work?
On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bd7tj$rh4f$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>>
Most of us have a CS degree. But then we go out into the real world, get a >>> job and find out what real programming on real products entails, not a load >>> of virtual academic naval gazing.
That's because it's not a trade school degree. It's not there to teach
you to program, it's there to teach you the fundamentals that you need to
properly understand programming.
No, it teaches you fundamentals of certain aspects of computer paradigms such as databases, graphics, AI. Most people into computers learn actual programming
long before they hit university.
Engineering schools are even more that way. They don't teach you much
engineering, but they give you all the background that you need to learn
engineering.
Programming isn't pure engineering - its a combination of engineering, logic, art and a trade.
If you just want a job, getting one of these degrees is not for you. It's >> not there for that.
Bill Gates never earned a degree. He seemed to do ok.
On Fri, 23 Oct 2026 16:37:37 GMT
Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Considering how much of my career I've spent working around poor
design decisions and outright bugs in Windows, I'd say that is
self-evident.
AFAIK you can't pin that one on him; the Tandy Model 100 was the last
product he actually wrote code for, and that came out in '83, right at
the beginning of development on Windows 1.0. Dunno that he did much on MS-DOS, either, as the core of that was Tim Paterson's work in, erm, "adapating" the design of CP/M to the 8086.
John Ames <commodorejohn@gmail.com> wrote:
AFAIK you can't pin that one on him; the Tandy Model 100 was the last >>product he actually wrote code for, and that came out in '83, right at
the beginning of development on Windows 1.0. Dunno that he did much on >>MS-DOS, either, as the core of that was Tim Paterson's work in, erm, >>"adapating" the design of CP/M to the 8086.
He continued doing code reviews well into the Win 7 era, and a lot of
people wound up having to clean up after him. He was always very hands-on.
I remember in 1978 him being the third tier tech support hotline for
MBASIC bugs. He was incredibly rude.
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>>You need an OS to do threading properly too. Theres a reason green threads >>>in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but >not a process library. Its perfectly possible to simulate a multiprocess >enviroment.
How do you think pure software versions of virtual machines work?
On 2026-10-23 05:28, David Brown wrote:
On 22/10/2026 22:25, James Kuyper wrote:
On 2026-10-22 12:02, Scott Lurndal wrote:The term in both the C and C++ standards is "abstract machine", but I
The C/C++ "Virtual Machine Model" as described in the language
specifications is an apple.
think it was quite obvious that this is Dan meant when he wrote "virtual
machine". ...
I suspected as much, but it seemed a sufficiently odd mistake that I
wasn't sure.
On 10/23/2026 1:03 AM, boltar@caprica.universe wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>,
<boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green
threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system.-a I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading
library but
not a process library. Its perfectly possible to simulate a multiprocess
enviroment. How do you think pure software versions of virtual
machines work?
Well, a process lib needs to have certain things. Imvvho, at least
access to robust mutex?
On Fri, 23 Oct 2026 08:05:13 -0000 (UTC)
boltar@caprica.universe wrote:
On Thu, 22 Oct 2026 22:48:29 +0300
Michael S <already5chosen@yahoo.com> gabbled:
On Thu, 22 Oct 2026 14:51:31 -0000 (UTC)
boltar@battlestar.co.uk wrote:
I agree that the work for a CS degree is useful. If nothing else
I understand more now.
Most of us have a CS degree.
I don't have it.
How do you know about most?
Oh I dunno, maybe 30 years in the industry working with probably
hundreds of different programmers.
My experience in industry beats yours by few years.
And my statistics differ - CS graduates are not majority of computer programmers.
Michael S wrote:I studied to be a physicist, got a BS from Caltech, and did postgraduate
My experience in industry beats yours by few years.
And my statistics differ - CS graduates are not majority of computer
programmers.
In the 70s and early 80s there was little demand for people with
graduate degrees in physics. Most of my fellow students went on to work
in computer science or drove taxis when their postdoctoral positions expired.
I am a lousy driver and so-so programmer (at best) so I was forced to
stick with it.
On 2026-10-23 17:40, William Hyde wrote:
Michael S wrote:I studied to be a physicist, got a BS from Caltech, and did postgraduate
My experience in industry beats yours by few years.
And my statistics differ - CS graduates are not majority of computer
programmers.
In the 70s and early 80s there was little demand for people with
graduate degrees in physics. Most of my fellow students went on to work
in computer science or drove taxis when their postdoctoral positions
expired.
I am a lousy driver and so-so programmer (at best) so I was forced to
stick with it.
work at Cambridge. I reached that point in the 90s. I learned computer programming only with the intent of using it as a tool in support of my physics. That idea foundered on two rocks: while I am very good at understanding advanced physics, I'm not particularly good at the practicalities of experimental physics, and my imagination isn't good
enough to make a good theoretical physicist. I ended up being a
programmer who specialized in scientific programming, rather than a
scientist who uses computer programs.
On 10/15/2026 2:13 PM, Lynn McGuire wrote:
On 10/15/2026 10:05 AM, Scott Dorsey wrote:
Lynn McGuire-a <lynnmcguire5@gmail.com> wrote:
Huh, so somebody has actually built a decent decompiler.-a Why do I
doubt
this even though ESR says otherwise?
Because decompiling some languages isn't that hard.-a Humans can do it
pretty
well, although it's harder for machines.-a It helps a lot if you have
a symbol
table (which it sounds like they did in the example ESR cites).
Now... that said... I wouldn't trust anything ESR ever says and I
would not
hold him up as an authority.
And he has a translator from Borland Pascal to Rust?
That seems like a step down, doesn't it?
--scott
Yes on the step down to Rust.-a I wrote a lot of Turbo Pascal code back
in the 1980s but I have to admit that I am a C++ fanboi through and
through.-a And at my age, it will hard to change my mind on that unless
you are writing embedded code.
I have translated over 200,000 lines of Fortran 66/77 code to C++ this
year so far.-a Trying to get to 300,000 lines of Fortran 66/77 code
before the end of the year.
Lynn
Be sure to let us know, we'll throw a party.
Actually, I'm close enough that that's possible.
Why does Mozilla Firefox update itself just about every week?
On 10/23/2026 11:06 AM, Peter Flass wrote:
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Bill Gates wrote the Microsoft Basic compiler and interpreter for the
Altair 8080 in 2K of ram using assembly language. Take that as you will.
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote: >>On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads >>>>in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but >>not a process library. Its perfectly possible to simulate a multiprocess >>enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
On 10/23/26 01:01, boltar@caprica.universe wrote:
On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bd7tj$rh4f$1@dont-email.me>,-a <boltar@battlestar.co.uk>
wrote:
Most of us have a CS degree. But then we go out into the real world,
get a
job and find out what real programming on real products entails, not
a load
of virtual academic naval gazing.
That's because it's not a trade school degree.-a It's not there to teach >>> you to program, it's there to teach you the fundamentals that you
need to
properly understand programming.
No, it teaches you fundamentals of certain aspects of computer
paradigms such
as databases, graphics, AI. Most people into computers learn actual
programming
long before they hit university.
Engineering schools are even more that way.-a They don't teach you much
engineering, but they give you all the background that you need to learn >>> engineering.
Programming isn't pure engineering - its a combination of engineering,
logic,
art and a trade.
If you just want a job, getting one of these degrees is not for you.
It's
not there for that.
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads >>>>>in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an >>>>operating system. I mean, POSIX already does an ok job of >>>>standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but >>>not a process library. Its perfectly possible to simulate a multiprocess >>>enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote: >>> On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but >>> not a process library. Its perfectly possible to simulate a multiprocess >>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
boltar@caprica.universe writes:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>>On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> >wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an >>>>>operating system. I mean, POSIX already does an ok job of >>>>>standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but >>>>not a process library. Its perfectly possible to simulate a multiprocess >>>>enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
It doesn't. It does have an abstraction wrapper around
whatever threading support the target host has.
boltar@caprica.universe writes:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but
not a process library. Its perfectly possible to simulate a multiprocess >>>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
It doesn't. It does have an abstraction wrapper around
whatever threading support the target host has.
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads >>>>>in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an >>>>operating system. I mean, POSIX already does an ok job of >>>>standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but >>>not a process library. Its perfectly possible to simulate a multiprocess >>>enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
Still, somebody had to decide to make the MS-DOS COPY command refuse
to copy zero-length files - something which CP/M's PIP did happily.
On 10/23/2026 11:06 AM, Peter Flass wrote:
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Bill Gates wrote the Microsoft Basic compiler and interpreter for the >>Altair 8080 in 2K of ram using assembly language. Take that as you will.
Gates when he put his mind to it could certainly program. Even Sinclair >required 4K for BASIC in the ZX80 for example. But some of his technical
(and business) decisions leave a lot to be desired.
On 10/24/26 01:21, boltar@caprica.universe wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but
not a process library. Its perfectly possible to simulate a multiprocess >>>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
You can have co-operative threads. IBM CICS used to run lots of threads >(tasks) concurrently, and ran them well.
In article <11bhpo6$2lpjl$1@dont-email.me>, <boltar@caprica.universe> wrote:
Lynn McGuire <lynnmcguire5@gmail.com> gabbled:
On 10/23/2026 11:06 AM, Peter Flass wrote:Gates when he put his mind to it could certainly program. Even Sinclair
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Bill Gates wrote the Microsoft Basic compiler and interpreter for the
Altair 8080 in 2K of ram using assembly language. Take that as you will. >>
required 4K for BASIC in the ZX80 for example. But some of his technical
(and business) decisions leave a lot to be desired.
But the ZX80 (and most later MBASICs) had floating point.
--scott
In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but
not a process library. Its perfectly possible to simulate a multiprocess >>>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
- Dan C.
boltar@caprica.universe writes:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but
not a process library. Its perfectly possible to simulate a multiprocess >>>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
It doesn't. It does have an abstraction wrapper around
whatever threading support the target host has.
In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but
not a process library. Its perfectly possible to simulate a multiprocess >>>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but
not a process library. Its perfectly possible to simulate a multiprocess >>>>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual
memory, who knows?)
Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
Still, somebody had to decide to make the MS-DOS COPY command refuse
to copy zero-length files - something which CP/M's PIP did happily.
That's a bug and not a feature. Sometimes you want to have a zero-length file in place as a semaphore.
In article <11bj08r$309uk$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>,
<boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason
green threads in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading
library but not a process library. Its perfectly possible to
simulate a multiprocess enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual >memory, who knows?)
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
- Dan C.
I ignore this newsgroup, so I am unlikely to notice a reply.In case you do, I thank you for your advice which I will consider later
On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <11bj08r$309uk$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>,
<boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason
green threads in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading
library but not a process library. Its perfectly possible to
simulate a multiprocess enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual
memory, who knows?)
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
- Dan C.
First, he was talking about C++. Unlike me, he does not appear to care
about C.
Second, while in theory threads can be implemented by C++
compilers+language support library, in practice I had never seen it
done.
All I had seen is C++ threads implemented in library as thin
wrapper atop of the OS (or RT executive) implementation.
I can not see while the same can't be done for processes, with
API modeled on posix_spawn() or Windows CreateProcess().
It does not look like variety in this field is bigger than in case of >threads. More like it is smaller.
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
In article <20261025011151.000038ef@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <11bj08r$309uk$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>,
<boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a
reason green threads in java were a joke.
Weird that you think you need a operating system for
threads, yet you want C to standardize processes which also
... need an operating system. I mean, POSIX already does
an ok job of standardizing the sorts of process-y things
you would expect from, you know, an operating system.
I'm simply pointing out the inconsistency in having a
threading library but not a process library. Its perfectly
possible to simulate a multiprocess enviroment.
So write a simulator in your language of choice. You don't
need the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A
process runs in its own address space. (at least these days,
before virtual memory, who knows?)
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
- Dan C.
First, he was talking about C++. Unlike me, he does not appear to
care about C.
First, he's a big boy, and I'm sure he can answer for himself.
But ok then, C++, not C. The questions still stand.
Second, while in theory threads can be implemented by C++ >compilers+language support library, in practice I had never seen it
done.
This is not saying much about anything aside from the countours
of your own experience, I'm afraid.
All I had seen is C++ threads implemented in library as thin
wrapper atop of the OS (or RT executive) implementation.
In the late 1990s, into the early 2000s, most "threads" on
Unix-style systems were implemented in userspace, in the C
library, often by exposing the "normal" system call endpoints
in the library, but making them thin wrappers around equivalent
asynchronous system calls.
There was even a paper about using the Xinu pedagogical system
from Doug Comer to implement something very close to threads on
4.2BSD, with signals and a context saving/restoration primitive
to approximate a timer interrupt.
For a more recent historical example the FreeBSD MP library was
initially implemented this way, as were pre-LinuxThreasd threads
on Linux; Solaris threads up until Solaris 2.6 or so similarly.
Of course, it wasn't a great way to do things because if
something _did_ block...well, there went your concurrency.
Making Unix systems multithreaded was challenging because of
decades of software that was written assuming a single-threaded
userspace environment (the kernel had been "multithreaded" since
very near the start, even if much of the system was written
assuming a single processor; but parallelism is not the same
thing as concurrency), and this was compounded because people
were trying to implement complex M:N threading models; Sun did
this, and FreeBSD tried with their KSEs; the Linux people did
not. While cool in theory, M:N threading relied on very
specific usage patterns to work well in practice, and almost no
one actually wrote software that way, so you ended up with
userspace threads fighting the kernel scheeduler, and vice
versa.
More recently, the Akaros research system introduced the notion
of a "many-core process" and pushed fine-grained "thread"
scheduling entirely to userspace; the kernel is totally unaware
of how userspace schedules anything. That system uses an N:C
model, where $C$ is the number of *cores* assigned to a process
(all system calls in Akaros are asychronous by design, to avoid
the pitfalls of user-threads blocking on synchronous kernel
services that beset Unix).
I can not see while the same can't be done for processes, with
API modeled on posix_spawn() or Windows CreateProcess().
C, and C++, have had `system()` for as long as I can remember,
if you just want to run a program (note that both `posix_spawn`
and `CreateProcess` take the names of programs to run in that
new process).
It does not look like variety in this field is bigger than in case of >threads. More like it is smaller.
Nope. But if you think differently, see the questions above.
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
POSIX has all of that. POSIX also has a process model. Why not
just make POSIX a part of the language, then? (Answer that and
you may start to understand why this is harder than it looks
for C++ [and C].)
- Dan C.
On 2026-10-24, Scott Dorsey <kludge@panix.com> wrote:
Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
Still, somebody had to decide to make the MS-DOS COPY command refuse
to copy zero-length files - something which CP/M's PIP did happily.
That's a bug and not a feature. Sometimes you want to have a zero-length
file in place as a semaphore.
Exactly. Another case is a month-to-date accumulator
at the beginning of the month.
Still, I've heard some pretty amazing attempts to justify this
design flaw as a feature.
In article <11bhpo6$2lpjl$1@dont-email.me>, <boltar@caprica.universe> wrote:
Lynn McGuire <lynnmcguire5@gmail.com> gabbled:
On 10/23/2026 11:06 AM, Peter Flass wrote:
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Bill Gates wrote the Microsoft Basic compiler and interpreter for the >>>Altair 8080 in 2K of ram using assembly language. Take that as you will.
Gates when he put his mind to it could certainly program. Even Sinclair >>required 4K for BASIC in the ZX80 for example. But some of his technical >>(and business) decisions leave a lot to be desired.
But the ZX80 (and most later MBASICs) had floating point.
--scott
In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe> wrote: >>On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>>On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> >wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an >>>>>operating system. I mean, POSIX already does an ok job of >>>>>standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but >>>>not a process library. Its perfectly possible to simulate a multiprocess >>>>enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
In article <11bhpo6$2lpjl$1@dont-email.me>, <boltar@caprica.universe> wrote: >>Lynn McGuire <lynnmcguire5@gmail.com> gabbled:
On 10/23/2026 11:06 AM, Peter Flass wrote:
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Bill Gates wrote the Microsoft Basic compiler and interpreter for the >>>Altair 8080 in 2K of ram using assembly language. Take that as you will.
Gates when he put his mind to it could certainly program. Even Sinclair >>required 4K for BASIC in the ZX80 for example. But some of his technical >>(and business) decisions leave a lot to be desired.
But the ZX80 (and most later MBASICs) had floating point.
In article <11bif5s$2pam0$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
You can have co-operative threads. IBM CICS used to run lots of threads >>(tasks) concurrently, and ran them well.
When I learned C, there was no threading and there were only different >processes, so you had to do a fork and then synchronize with the other >process. This wasn't a dealbreaker and we did plenty of stuff that way,
but having threads available was very nice and made for many operations >becoming more convenient to write.
In article <11bj08r$309uk$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe> >wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> >wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> >wrote:
You need an OS to do threading properly too. Theres a reason green >threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library >but
not a process library. Its perfectly possible to simulate a multiprocess >>>>>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual >>memory, who knows?)
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
In article <20261025011151.000038ef@yahoo.com>,
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
POSIX has all of that. POSIX also has a process model. Why not
just make POSIX a part of the language, then? (Answer that and
you may start to understand why this is harder than it looks
for C++ [and C].)
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe> wrote:
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
- Dan C.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual
memory, who knows?)
I supported an IBM 9370 back in the 90s and whatever operating system
it ran (completely different to the 3090 mainframe with JCL, etc it
was supposed to replace) didn't allow zero length files.
On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <11bj08r$309uk$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>,
<boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason >>>>>>>>> green threads in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an >>>>>>>> operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading
library but not a process library. Its perfectly possible to
simulate a multiprocess enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual
memory, who knows?)
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
- Dan C.
First, he was talking about C++. Unlike me, he does not appear to care
about C.
Second, while in theory threads can be implemented by C++
compilers+language support library, in practice I had never seen it
done. All I had seen is C++ threads implemented in library as thin
wrapper atop of the OS (or RT executive) implementation.
I can not see while the same can't be done for processes, with
API modeled on posix_spawn() or Windows CreateProcess().
It does not look like variety in this field is bigger than in case of threads. More like it is smaller.
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bhpo6$2lpjl$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>Lynn McGuire <lynnmcguire5@gmail.com> gabbled:
On 10/23/2026 11:06 AM, Peter Flass wrote:Gates when he put his mind to it could certainly program. Even Sinclair >>>required 4K for BASIC in the ZX80 for example. But some of his technical >>>(and business) decisions leave a lot to be desired.
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Bill Gates wrote the Microsoft Basic compiler and interpreter for the >>>>Altair 8080 in 2K of ram using assembly language. Take that as you will. >>>
But the ZX80 (and most later MBASICs) had floating point.
The ZX80 ran Sinclair Basic, it had nothing to do with MS and it was integer >only. The ZX81 had flowing point basic and had an 8K ROM which is still >bloody impressive.
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261025011151.000038ef@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
[snip]
Second, while in theory threads can be implemented by C++
compilers+language support library, in practice I had never seen it
done.
This is not saying much about anything aside from the countours
of your own experience, I'm afraid.
[snip history showing a long line of "OS Threads" implemented
as a library]
How any of this trivia has anything to do with real-world
implementations of C++11 threads?
I mentioned that in one of my earlier responses to boltar.
However there exist situation in which system() is not a satisfactory >replacement for spawn(), most often because overhead of launching shell >sometimes matters.
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >model/api are? Yet somehow C++ provides a common wrapper for both. There is >no reason the same can't be done for processes and your irrelevant waffle >about past issues of threading on *nix don't change that.
Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:
I supported an IBM 9370 back in the 90s and whatever operating system
it ran (completely different to the 3090 mainframe with JCL, etc it
was supposed to replace) didn't allow zero length files.
VM/CMS?
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading
model/api are? Yet somehow C++ provides a common wrapper for both. There is >> no reason the same can't be done for processes and your irrelevant waffle
about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
- Dan C.
On 10/25/26 02:30, Thomas Koenig wrote:
Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:
I supported an IBM 9370 back in the 90s and whatever operating system
it ran (completely different to the 3090 mainframe with JCL, etc it
was supposed to replace) didn't allow zero length files.
VM/CMS?
Or some version of DOD/360? They had a couple of versions, I think. They kept trying to make it easier to install and maintain, but it was still
DOS.
Those times I want to run something now I use VM, because it is so much simpler.
On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
- Dan C.
First, he was talking about C++. Unlike me, he does not appear to care
about C.
Second, while in theory threads can be implemented by C++
compilers+language support library, in practice I had never seen it
done. All I had seen is C++ threads implemented in library as thin
wrapper atop of the OS (or RT executive) implementation.
I can not see while the same can't be done for processes, with
API modeled on posix_spawn() or Windows CreateProcess().
It does not look like variety in this field is bigger than in case of >threads. More like it is smaller.
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
In article <20261025084234.0000449c@yahoo.com>,<snip>
Michael S <already5chosen@yahoo.com> wrote:
How any of this trivia has anything to do with real-world
implementations of C++11 threads?
Your statement, "while in theory threads can be implemented by
C++ compilers+language support library, in practice I had never
seen it done" is probably strictly true: you, individually, have
never seen it done.
But that does not imply that it has never been done. In
fact, it has; many times over. There are complications, but it
can be done. That is what I was telling you, supported by
examples.
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote: >>On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>model/api are? Yet somehow C++ provides a common wrapper for both. There is >>no reason the same can't be done for processes and your irrelevant waffle >>about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
cross@spitfire.i.gajendra.net (Dan Cross) writes:
In article <20261025084234.0000449c@yahoo.com>,<snip>
Michael S <already5chosen@yahoo.com> wrote:
How any of this trivia has anything to do with real-world
implementations of C++11 threads?
Your statement, "while in theory threads can be implemented by
C++ compilers+language support library, in practice I had never
seen it done" is probably strictly true: you, individually, have
never seen it done.
But that does not imply that it has never been done. In
fact, it has; many times over. There are complications, but it
can be done. That is what I was telling you, supported by
examples.
Although it does, generally, rely on specific operating system
interfaces (e.g. makecontext, setcontext, et alia).
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>>model/api are? Yet somehow C++ provides a common wrapper for both. There is >>>no reason the same can't be done for processes and your irrelevant waffle >>>about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
Stop playing games - you don't get to answer a question with a question.
Given I've been programming on unix for over 30 years and have written dozens >of applications using multi process and multi threading and sometimes using both
I'm quite well aware of the differences. Perhaps you arn't which is why you >need me to tell you. Well go do your own research.
In the meantime I'll ask one last time - why do you think C++ can provide
a threading wrapper API but not a multi process one?
Take your time.
In article <YHpDS.27364$9b8f.4666@fx39.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
cross@spitfire.i.gajendra.net (Dan Cross) writes:
In article <20261025084234.0000449c@yahoo.com>,<snip>
Michael S <already5chosen@yahoo.com> wrote:
How any of this trivia has anything to do with real-world >>>>implementations of C++11 threads?
Your statement, "while in theory threads can be implemented by
C++ compilers+language support library, in practice I had never
seen it done" is probably strictly true: you, individually, have
never seen it done.
But that does not imply that it has never been done. In
fact, it has; many times over. There are complications, but it
can be done. That is what I was telling you, supported by
examples.
Although it does, generally, rely on specific operating system
interfaces (e.g. makecontext, setcontext, et alia).
That's true. But no one said that one can use strict ISO C++ to
implement the C++ standard library.
Regardless, if you can set the stack pointer, you can build a
reasonable cooperative threading library purely in userspace,
without the OS caring.
In article <11bl9qm$10h8f$1@dont-email.me>, <boltar@caprica.universe> wrote: >>On Sun, 25 Oct 2026 13:34:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>>>model/api are? Yet somehow C++ provides a common wrapper for both. There is >>>>no reason the same can't be done for processes and your irrelevant waffle >>>>about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
Stop playing games - you don't get to answer a question with a question.
In other words, you don't know.
In the meantime I'll ask one last time - why do you think C++ can provide
a threading wrapper API but not a multi process one?
You've got system(), right? What, precisely, do you want this
On 10/25/26 06:34, Dan Cross wrote:
[snip]
What do you think that a "thread" is?
What do you think that a "process" is?
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
with a question.[snip]
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
Stop playing games - you don't get to answer a question
In other words, you don't know.
Oh do piss off you bore, i'm not going to humour you while
you try to unpaint
yourself from a corner. You clearly have no idea why C++
implements one API
but not the other but you wanted to try and sound clever
anyway. Whoops, didn't
turn out quite how you expected did it?
C++ can provideIn the meantime I'll ask one last time - why do you think
a threading wrapper API but not a multi process one?
You've got system(), right? What, precisely, do you want this
system?? ROTFL!! :)
Oh dear, you really have no clue!
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
Regardless, if you can set the stack pointer, you can build a
reasonable cooperative threading library purely in userspace,
without the OS caring.
Oh really? You seem to have forgotten about the program
counter not to
mentioning pushing and popping all the other cpu registers
and flags at context
switch.
On 10/25/26 06:34, Dan Cross wrote:
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading
model/api are? Yet somehow C++ provides a common wrapper for both. There >> is
no reason the same can't be done for processes and your irrelevant waffle >> about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
- Dan C.
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
In article <11bker0$2pa7q$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Sat, 24 Oct 2026 13:53:39 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bhpo6$2lpjl$1@dont-email.me>, <boltar@caprica.universe> wrote:
Lynn McGuire <lynnmcguire5@gmail.com> gabbled:
On 10/23/2026 11:06 AM, Peter Flass wrote:Gates when he put his mind to it could certainly program. Even Sinclair >>>> required 4K for BASIC in the ZX80 for example. But some of his technical >>>> (and business) decisions leave a lot to be desired.
Bill Gates wrote the Microsoft Basic compiler and interpreter for the >>>>> Altair 8080 in 2K of ram using assembly language. Take that as you will. >>>>Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though. >>>>>
But the ZX80 (and most later MBASICs) had floating point.
The ZX80 ran Sinclair Basic, it had nothing to do with MS and it was integer >> only. The ZX81 had flowing point basic and had an 8K ROM which is still
bloody impressive.
I did not realize that the ZX80 was integer only! I thought it was more
or less like the ZX81 with everything stuffed into an asic.
--scott
In article <11bl7vr$3nprb$2@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/25/26 06:34, Dan Cross wrote:
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe>
wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>>> model/api are? Yet somehow C++ provides a common wrapper for both. There >>>> is
no reason the same can't be done for processes and your irrelevant waffle >>>> about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
- Dan C.
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
For that matter, this entire thread has ceased to have anything to do
with rec.arts.sf.written.
On 10/25/2026 1:19 PM, Robert Woodward wrote:
In article <11bl7vr$3nprb$2@dont-email.me>,
-a Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/25/26 06:34, Dan Cross wrote:
In article <11bkfcc$104cc$1@dont-email.me>,-a <boltar@caprica.universe> >>>> wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>>>> model/api are? Yet somehow C++ provides a common wrapper for both.
There
is
no reason the same can't be done for processes and your irrelevant
waffle
about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
-a-a-a-a- Dan C.
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
For that matter, this entire thread has ceased to have anything to do
with rec.arts.sf.written.
Based on 40+ years of usenet experience, the only thing which will stop
the cross posting is the death of this thread.
pt
In article <11bl7vr$3nprb$2@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/25/26 06:34, Dan Cross wrote:
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe>
wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>>> model/api are? Yet somehow C++ provides a common wrapper for both. There >>>> is
no reason the same can't be done for processes and your irrelevant waffle >>>> about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
- Dan C.
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
For that matter, this entire thread has ceased to have anything to do
with rec.arts.sf.written.
On 25/10/2026 18:19, Robert Woodward wrote:
In article <11bl7vr$3nprb$2@dont-email.me>,
-a Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/25/26 06:34, Dan Cross wrote:
In article <11bkfcc$104cc$1@dont-email.me>,-a <boltar@caprica.universe> >>>> wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>>>> model/api are? Yet somehow C++ provides a common wrapper for both.
There
is
no reason the same can't be done for processes and your irrelevant
waffle
about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
-a-a-a-a- Dan C.
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
For that matter, this entire thread has ceased to have anything to do
with rec.arts.sf.written.
Was it ever relevant to that group?-a At least one person in this thread
is renowned for his irritating habit of adding every newsgroup he can
think of to lists.-a "This post is in English - I'll add alt.languages.english to the list.-a I see there was a number mentioned - I've added sci.maths for their thoughts.-a I've just thought about
thoughts, so alt.philosophy is needed too".
David Brown wrote:
On 25/10/2026 18:19, Robert Woodward wrote:
In article <11bl7vr$3nprb$2@dont-email.me>,
-a Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/25/26 06:34, Dan Cross wrote:
In article <11bkfcc$104cc$1@dont-email.me>,-a <boltar@caprica.universe> >>>>> wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows
threading
model/api are? Yet somehow C++ provides a common wrapper for both. >>>>>> There
is
no reason the same can't be done for processes and your irrelevant >>>>>> waffle
about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
-a-a-a-a- Dan C.
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
For that matter, this entire thread has ceased to have anything to do
with rec.arts.sf.written.
Was it ever relevant to that group?-a At least one person in this
thread is renowned for his irritating habit of adding every newsgroup
he can think of to lists.-a "This post is in English - I'll add
alt.languages.english to the list.-a I see there was a number mentioned
- I've added sci.maths for their thoughts.-a I've just thought about
thoughts, so alt.philosophy is needed too".
Sorry about that. I only did it because Eternal September, if I take
away one of the Newsgroups: listings, it won't let me post. In such a
case it only allows 3 newsgroups. That won't do for this thread.
On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bj08r$309uk$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/24/26 09:41, Dan Cross wrote:wrote:
In article <11bhppd$2lpkc$1@dont-email.me>,
<boltar@caprica.universe>
wrote:On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>,
<boltar@caprica.universe>
wrote:On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>,
<boltar@battlestar.co.uk>
threads
You need an OS to do threading properly too. Theres a reason >>>>>>>> green
butin java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an >>>>>>> operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a
threading library
not a process library. Its perfectly possible to simulate a
multiprocess enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A
process runs in its own address space. (at least these days, before >>virtual memory, who knows?)
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
Who mentioned C? I was talking about C++ which has a threading API
already. Do try and keep up.
In article <11bl7vr$3nprb$2@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
For that matter, this entire thread has ceased to have anything to do
with rec.arts.sf.written.
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261025011151.000038ef@yahoo.com>,
Now, would it be the first thing I would want like addition to C++ >>standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
POSIX has all of that. POSIX also has a process model. Why not
just make POSIX a part of the language, then? (Answer that and
you may start to understand why this is harder than it looks
for C++ [and C].)
No, it isn't. How similar do you think the posix and windows threading model/api are? Yet somehow C++ provides a common wrapper for both.
There is no reason the same can't be done for processes and your
irrelevant waffle about past issues of threading on *nix don't change
that.
On Sat, 24 Oct 2026 13:57:02 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bif5s$2pam0$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
You can have co-operative threads. IBM CICS used to run lots of threads
(tasks) concurrently, and ran them well.
When I learned C, there was no threading and there were only different
processes, so you had to do a fork and then synchronize with the other
process. This wasn't a dealbreaker and we did plenty of stuff that way,
but having threads available was very nice and made for many operations
becoming more convenient to write.
Unfortunately most win32 programmers don't really understand multiprocess programming because the w32 API is so borked so use threads even when seperate process would be more appropriate.
On Sat, 24 Oct 2026 13:57:02 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bif5s$2pam0$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
You can have co-operative threads. IBM CICS used to run lots of threads
(tasks) concurrently, and ran them well.
When I learned C, there was no threading and there were only different
processes, so you had to do a fork and then synchronize with the other
process. This wasn't a dealbreaker and we did plenty of stuff that way,
but having threads available was very nice and made for many operations
becoming more convenient to write.
Unfortunately most win32 programmers don't really understand multiprocess programming because the w32 API is so borked so use threads even when seperate process would be more appropriate.
On Sat, 24 Oct 2026 16:41:22 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> >> wrote:
You need an OS to do threading properly too. Theres a reason green threads
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an
operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library but
not a process library. Its perfectly possible to simulate a multiprocess >>>>> enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
The differences are utterly irrelevant when it comes to prividing a common API to the functionality but thank you for demonstrating you had no answer
to my question.
Bill Gates wrote the Microsoft Basic compiler and interpreter for the
Altair 8080 in 2K of ram using assembly language. Take that as you will.
On Sun, 25 Oct 2026 16:15:21 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <YHpDS.27364$9b8f.4666@fx39.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
cross@spitfire.i.gajendra.net (Dan Cross) writes:
In article <20261025084234.0000449c@yahoo.com>,<snip>
Michael S <already5chosen@yahoo.com> wrote:
How any of this trivia has anything to do with real-world
implementations of C++11 threads?
Your statement, "while in theory threads can be implemented by
C++ compilers+language support library, in practice I had never
seen it done" is probably strictly true: you, individually, have
never seen it done.
But that does not imply that it has never been done. In
fact, it has; many times over. There are complications, but it
can be done. That is what I was telling you, supported by
examples.
Although it does, generally, rely on specific operating system
interfaces (e.g. makecontext, setcontext, et alia).
That's true. But no one said that one can use strict ISO C++ to
implement the C++ standard library.
Regardless, if you can set the stack pointer, you can build a
reasonable cooperative threading library purely in userspace,
without the OS caring.
Oh really? You seem to have forgotten about the program counter not to mentioning pushing and popping all the other cpu registers and flags at context
switch.
The Apple ][ was also integer only. The Apple ][+ had floating point.
The top 16k of memory was ROM supporting the OS and BASIC. Relatively
roomy compared to the ZX80/81.
pt--
On Sun, 25 Oct 2026 13:34:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>>model/api are? Yet somehow C++ provides a common wrapper for both. There is >>>no reason the same can't be done for processes and your irrelevant waffle >>>about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
Stop playing games - you don't get to answer a question with a question. Given I've been programming on unix for over 30 years and have written dozens of applications using multi process and multi threading and sometimes using both
I'm quite well aware of the differences. Perhaps you arn't which is why you need me to tell you. Well go do your own research.
In the meantime I'll ask one last time - why do you think C++ can provide
a threading wrapper API but not a multi process one?
Take your time.
Cryptoengineer <petertrei@gmail.com> wrote:
The Apple ][ was also integer only. The Apple ][+ had floating point.
The top 16k of memory was ROM supporting the OS and BASIC. Relatively
roomy compared to the ZX80/81.
Yes, the INTBASIC was Apple code, while APPLESOFT BASIC was written by Microsoft on contract to Apple. APPLESOFT worked pretty well aside from programmable functions. It could do realtime FFTs at 0.5 samp/sec which
was good enough for some interesting things.
You could upgrade the roms in your original Apple ][ to the ][+ roms
for what seemed like a fortune to me at the time but which was probably
quite reasonable. I think you lost Sweet-16 in the process though.
--scott
pt
Bill Gates wrote the Microsoft Basic compiler and interpreter for the
Altair 8080 in 2K of ram using assembly language. Take that as you will.
On Sun, 25 Oct 2026 08:41:48 -0000 (UTC)
boltar@caprica.universe wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261025011151.000038ef@yahoo.com>,
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
POSIX has all of that. POSIX also has a process model. Why not
just make POSIX a part of the language, then? (Answer that and
you may start to understand why this is harder than it looks
for C++ [and C].)
No, it isn't. How similar do you think the posix and windows threading
model/api are? Yet somehow C++ provides a common wrapper for both.
Actually, implementing C++11 (or C11) threads fully in user space on pre-Vista Win32 (i.e. before addition of support for conditional
variables to OS API) would be quite challenging. I don't know if
anybody bothered.
I think that it is possible, but if you want it robust then it (cond. variables) will cost you significant overhead relatively to "native" synchronization primitives.
There is no reason the same can't be done for processes and your
irrelevant waffle about past issues of threading on *nix don't change
that.
Dick-measuring competitions are integral part of Usenet tradition.
On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bj08r$309uk$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
On 10/24/26 09:41, Dan Cross wrote:wrote:
In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe>
wrote:On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>, <boltar@caprica.universe>
threadsOn Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>, <boltar@battlestar.co.uk> >> wrote:
You need an OS to do threading properly too. Theres a reason green
in java were a joke.
Weird that you think you need a operating system for threads,
yet you want C to standardize processes which also ... need an >>>>>>>> operating system. I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect
from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading library >> but
not a process library. Its perfectly possible to simulate a multiprocess
enviroment.
So write a simulator in your language of choice. You don't need
the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is? And how is it
different from a _process_? For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual
memory, who knows?)
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
Who mentioned C? I was talking about C++ which has a threading API already. Do try and keep up.
On Sat, 24 Oct 2026 12:17:47 -0700
Peter Flass <Peter@Iron-Spring.com> gabbled:
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>,
<boltar@caprica.universe> wrote:
What, pray tell, do you think that a _thread_ is?-a And how is it
different from a _process_?-a For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
-a-a-a-a- Dan C.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual
memory, who knows?)
With copy-on-write process models the actual difference is a bit less
clear cut.
Cryptoengineer <petertrei@gmail.com> wrote:
The Apple ][ was also integer only. The Apple ][+ had floating point.
The top 16k of memory was ROM supporting the OS and BASIC. Relatively
roomy compared to the ZX80/81.
Yes, the INTBASIC was Apple code, while APPLESOFT BASIC was written by Microsoft on contract to Apple. APPLESOFT worked pretty well aside from programmable functions. It could do realtime FFTs at 0.5 samp/sec which
was good enough for some interesting things.
You could upgrade the roms in your original Apple ][ to the ][+ roms
for what seemed like a fortune to me at the time but which was probably
quite reasonable. I think you lost Sweet-16 in the process though.
--scott
pt
On 26/10/2026 06:19, Robert Woodward wrote:
In article <11bl7vr$3nprb$2@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
snip
I vote that alt.folklore.computers gets pruned from the list of
recipients, as this discussion seems irrelevant here.
For that matter, this entire thread has ceased to have anything to do
with rec.arts.sf.written.
Yes. You are correct, but there are several from r.a.sf.written making a contribution and although it is mainly above my pay grade, I am still reading. In Thunderbird, it is extremely easy to mark a thread as
ignored after which you will not be annoyed by further posts on that
topic. Easier than complaining.
Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:
I supported an IBM 9370 back in the 90s and whatever operating system
it ran (completely different to the 3090 mainframe with JCL, etc it
was supposed to replace) didn't allow zero length files.
VM/CMS?
In article <11blaui$2q6vd$1@dont-email.me>, <boltar@caprica.universe> wrote: >>anyway. Whoops, didn't
turn out quite how you expected did it?
Actually, it "turned out" juat about exactly as I expected it
would.
Oh dear, you really have no clue!
You're snotty little attitude aside, I note that you can't even
arriculate what, exactly, it is that you want. "Argument by
insult" seems about par for the course here, but using that to
hide your ignorance both doesn't work and makes you look
incredbily insecure.
Anyway, go ahead and keep flailing. Ta!
In article <11blaoq$2q6jk$1@dont-email.me>, <boltar@caprica.universe> wrote: >>On Sun, 25 Oct 2026 16:15:21 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
Regardless, if you can set the stack pointer, you can build a
reasonable cooperative threading library purely in userspace,
without the OS caring.
Oh really? You seem to have forgotten about the program
counter not to
mentioning pushing and popping all the other cpu registers
and flags at context
switch.
One last hint: where do you think those thjngs arw stored? If
you could define what a thread is, maybe you'd have a clue
about how those are handled. :-)
On Sun, 25 Oct 2026 08:41:48 -0000 (UTC)
boltar@caprica.universe wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261025011151.000038ef@yahoo.com>,
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
POSIX has all of that. POSIX also has a process model. Why not
just make POSIX a part of the language, then? (Answer that and
you may start to understand why this is harder than it looks
for C++ [and C].)
No, it isn't. How similar do you think the posix and windows threading
model/api are? Yet somehow C++ provides a common wrapper for both.
Actually, implementing C++11 (or C11) threads fully in user space on >pre-Vista Win32 (i.e. before addition of support for conditional
variables to OS API) would be quite challenging. I don't know if
anybody bothered.
I think that it is possible, but if you want it robust then it (cond. >variables) will cost you significant overhead relatively to "native" >synchronization primitives.
On 10/25/2026 1:34 AM, boltar@caprica.universe wrote:
On Sat, 24 Oct 2026 13:57:02 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bif5s$2pam0$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
You can have co-operative threads. IBM CICS used to run lots of threads >>>> (tasks) concurrently, and ran them well.
When I learned C, there was no threading and there were only different
processes, so you had to do a fork and then synchronize with the other
process. This wasn't a dealbreaker and we did plenty of stuff that way, >>> but having threads available was very nice and made for many operations
becoming more convenient to write.
Unfortunately most win32 programmers don't really understand multiprocess
programming because the w32 API is so borked so use threads even when
seperate process would be more appropriate.
Windows has what we need to run multi process. Even for a Mutex...
Remember WAIT_ABANDONED?
On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
The differences are utterly irrelevant when it comes to prividing a common >> API to the functionality but thank you for demonstrating you had no answer >> to my question.
Ummm... It is relevant. Every process has a single thread of execution,
but not all processes have multiple threads.
On Sun, 25 Oct 2026 09:30:12 -0000 (UTC), Thomas Koenig ><tkoenig@netcologne.de> wrote:
Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:
I supported an IBM 9370 back in the 90s and whatever operating system
it ran (completely different to the 3090 mainframe with JCL, etc it
was supposed to replace) didn't allow zero length files.
VM/CMS?
That's ringing a vague bell.
My time on the 9370 was short compared to the 3090, so all I can
remember were things like the file handling was MUCH simpler (no need
specify record types and block sizes and the foreground scripting
language REXX was much nicer than the CLIST we used on the mainframe -
it had stacks for storing and processing data, which was fun.
The only command I can remember was when I had my operator hat on and
a user wanted to access the 3422 tape drive I had to ATTACH the
physical 3 digit id of the tape drive to the logical 3 digit id they
were using (in retrospect I see this was its equivalent of unix mount >command).
that doesn't mean its a good idea.
On Sun, 25 Oct 2026 22:56:19 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Sun, 25 Oct 2026 08:41:48 -0000 (UTC)
boltar@caprica.universe wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261025011151.000038ef@yahoo.com>,
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
POSIX has all of that. POSIX also has a process model. Why not
just make POSIX a part of the language, then? (Answer that and
you may start to understand why this is harder than it looks
for C++ [and C].)
No, it isn't. How similar do you think the posix and windows threading
model/api are? Yet somehow C++ provides a common wrapper for both.
Actually, implementing C++11 (or C11) threads fully in user space on >>pre-Vista Win32 (i.e. before addition of support for conditional
variables to OS API) would be quite challenging. I don't know if
anybody bothered.
I think that it is possible, but if you want it robust then it (cond. >>variables) will cost you significant overhead relatively to "native" >>synchronization primitives.
C++ threading didn't have 3 level locking until 2017 making it effectively >useless IMO. Perhaps that was down to the lowest common denominator called >Windows.
boltar@caprica.universe writes:
C++ threading didn't have 3 level locking until 2017 making it effectively >>useless IMO. Perhaps that was down to the lowest common denominator called >>Windows.
Mind defining your terminology? "3 level locking", in particular?
Assigning a canonical "lock number" to each lock, and failing a lock
request for a lock with a lower number than that already held is
a design pattern that has been around since 1980 (in Burroughs
mainframes it was implemented in hardware). Easy enough to do
prior to C++17 in software.
And your assertion that a language that doesn't support it intrinsically
is "useless" is ridiculous.
In article <11bn80e$11hkj$1@dont-email.me>, <boltar@caprica.universe> wrote: >>Oh please, try a bit harder. You can do anything you want in ring 0 assembler,
that doesn't mean its a good idea.
As someone who is spending his morning writing 8051 code, I think it can be
a very very good idea.
On Sun, 25 Oct 2026 14:22:34 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
The differences are utterly irrelevant when it comes to prividing a
common
API to the functionality but thank you for demonstrating you had no
answer
to my question.
Ummm... It is relevant. Every process has a single thread of
execution, but not all processes have multiple threads.
No shit sherlock, thanks for the heads up. Your point is?
In article <11bnlrn$ghl$1@panix2.panix.com>,
Scott Dorsey <kludge@panix.com> wrote:
In article <11bn80e$11hkj$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>Oh please, try a bit harder. You can do anything you want in ring 0 assembler,
that doesn't mean its a good idea.
As someone who is spending his morning writing 8051 code, I think it can be >>a very very good idea.
The irony is that, by definition, if you are running something
in userspace, it's not in "Ring 0" anyway.
Basically that methinks you insult too much. Your wisdom here isn't
worth a sack of beans. I haven't learned one thing from you.
On Mon, 26 Oct 2026 14:41:54 GMT
scott@slp53.sl.home (Scott Lurndal) gabbled:
boltar@caprica.universe writes:
C++ threading didn't have 3 level locking until 2017 making it >>effectively useless IMO. Perhaps that was down to the lowest common >>denominator called Windows.
Mind defining your terminology? "3 level locking", in particular?
If you have to ask....
1. No lock
2. Write lock - Read only access, writer blocked until all readers
out of critic al section)
3. Read-write lock - all threads other than the one in section block)
This is basic stuff FFS. C++ finally got around to #2 with
shared_mutex in 2017 and its rather critical for certain algorithms.
Assigning a canonical "lock number" to each lock, and failing a lock >request for a lock with a lower number than that already held is
a design pattern that has been around since 1980 (in Burroughs
mainframes it was implemented in hardware). Easy enough to do
prior to C++17 in software.
Thats something else entirely.
And your assertion that a language that doesn't support it
intrinsically is "useless" is ridiculous.
Not useless then, just less useful.
On Sun, 25 Oct 2026 14:19:14 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/25/2026 1:34 AM, boltar@caprica.universe wrote:
On Sat, 24 Oct 2026 13:57:02 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bif5s$2pam0$1@dont-email.me>,
Peter Flass-a <Peter@Iron-Spring.com> wrote:
You can have co-operative threads. IBM CICS used to run lots of
threads
(tasks) concurrently, and ran them well.
When I learned C, there was no threading and there were only different >>>> processes, so you had to do a fork and then synchronize with the other >>>> process.-a This wasn't a dealbreaker and we did plenty of stuff that
way,
but having threads available was very nice and made for many operations >>>> becoming more convenient to write.
Unfortunately most win32 programmers don't really understand
multiprocess
programming because the w32 API is so borked so use threads even when
seperate process would be more appropriate.
Windows has what we need to run multi process. Even for a Mutex...
Remember WAIT_ABANDONED?
win32 can't do fork() making it effectively a totally useless API for a
lot of multiprocess development.
Creating a brand new process is fine if
you don't need any complicated shared state such as when kicking off something
on the command line or creating a pipe (something else win32 is shit at)
but
thats about it.
On Sun, 25 Oct 2026 17:14:18 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11blaui$2q6vd$1@dont-email.me>,
<boltar@caprica.universe> wrote:
anyway. Whoops, didn't
turn out quite how you expected did it?
Actually, it "turned out" juat about exactly as I expected it
would.
You have low expectations then.
Oh dear, you really have no clue!
You're snotty little attitude aside, I note that you can't even
Anyone who equates system() with multiprocess programming doesn't
know wtf they're talking about. Hows that for a snotty aside?
arriculate what, exactly, it is that you want. "Argument by
insult" seems about par for the course here, but using that to
hide your ignorance both doesn't work and makes you look
incredbily insecure.
Anyway, go ahead and keep flailing. Ta!
Go ahead and remain clueless.
On Sun, 25 Oct 2026 22:56:19 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Sun, 25 Oct 2026 08:41:48 -0000 (UTC)
boltar@caprica.universe wrote:
On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261025011151.000038ef@yahoo.com>,
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
POSIX has all of that. POSIX also has a process model. Why not
just make POSIX a part of the language, then? (Answer that and
you may start to understand why this is harder than it looks
for C++ [and C].)
No, it isn't. How similar do you think the posix and windows threading
model/api are? Yet somehow C++ provides a common wrapper for both.
Actually, implementing C++11 (or C11) threads fully in user space on
pre-Vista Win32 (i.e. before addition of support for conditional
variables to OS API) would be quite challenging. I don't know if
anybody bothered.
I think that it is possible, but if you want it robust then it (cond.
variables) will cost you significant overhead relatively to "native"
synchronization primitives.
C++ threading didn't have 3 level locking until 2017 making it effectively useless IMO. Perhaps that was down to the lowest common denominator called Windows.
On Sun, 25 Oct 2026 14:19:14 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/25/2026 1:34 AM, boltar@caprica.universe wrote:
On Sat, 24 Oct 2026 13:57:02 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bif5s$2pam0$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
You can have co-operative threads. IBM CICS used to run lots of
threads (tasks) concurrently, and ran them well.
When I learned C, there was no threading and there were only
different processes, so you had to do a fork and then synchronize
with the other process. This wasn't a dealbreaker and we did
plenty of stuff that way, but having threads available was very
nice and made for many operations becoming more convenient to
write.
Unfortunately most win32 programmers don't really understand
multiprocess programming because the w32 API is so borked so use
threads even when seperate process would be more appropriate.
Windows has what we need to run multi process. Even for a Mutex... >Remember WAIT_ABANDONED?
win32 can't do fork() making it effectively a totally useless API for
a lot of multiprocess development. Creating a brand new process is
fine if you don't need any complicated shared state such as when
kicking off something on the command line or creating a pipe
(something else win32 is shit at) but thats about it.
On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)Still don't really know what he means by 3 level locking. Using lock
boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 14:41:54 GMT
scott@slp53.sl.home (Scott Lurndal) gabbled:
boltar@caprica.universe writes:
C++ threading didn't have 3 level locking until 2017 making it
effectively useless IMO. Perhaps that was down to the lowest common
denominator called Windows.
Mind defining your terminology? "3 level locking", in particular?
If you have to ask....
1. No lock
2. Write lock - Read only access, writer blocked until all readers
out of critic al section)
3. Read-write lock - all threads other than the one in section block)
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11. https://learn.microsoft.com/en-us/windows/win32/sync/slim-reader-writer--srw--locks
Of course WinXP remained popular for few more years, approximately up
until 2nd half of 2010, but that too predates publication of C++11 in 2011-09.
This is basic stuff FFS. C++ finally got around to #2 with
shared_mutex in 2017 and its rather critical for certain algorithms.
Assigning a canonical "lock number" to each lock, and failing a lock
request for a lock with a lower number than that already held is
a design pattern that has been around since 1980 (in Burroughs
mainframes it was implemented in hardware). Easy enough to do
prior to C++17 in software.
Thats something else entirely.
And your assertion that a language that doesn't support it
intrinsically is "useless" is ridiculous.
Not useless then, just less useful.
I never ever used what you call "3 level locking", not even by mistake.
But then, I don't write complicated apps on "big" computers day in day
out.
On Sun, 25 Oct 2026 14:22:34 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
The differences are utterly irrelevant when it comes to prividing a
common
API to the functionality but thank you for demonstrating you had no
answer
to my question.
Ummm... It is relevant. Every process has a single thread of
execution, but not all processes have multiple threads.
No shit sherlock, thanks for the heads up. Your point is?
On 10/26/2026 12:45 PM, Michael S wrote:
On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 14:41:54 GMT
scott@slp53.sl.home (Scott Lurndal) gabbled:
boltar@caprica.universe writes:
C++ threading didn't have 3 level locking until 2017 making it
effectively useless IMO. Perhaps that was down to the lowest
common denominator called Windows.
Mind defining your terminology? "3 level locking", in
particular?
If you have to ask....
1. No lock
2. Write lock - Read only access, writer blocked until all readers
out of critic al section)
3. Read-write lock - all threads other than the one in section
block)
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11. https://learn.microsoft.com/en-us/windows/win32/sync/slim-reader-writer--srw--locks
Of course WinXP remained popular for few more years, approximately
up until 2nd half of 2010, but that too predates publication of
C++11 in 2011-09.
This is basic stuff FFS. C++ finally got around to #2 with
shared_mutex in 2017 and its rather critical for certain
algorithms.
Assigning a canonical "lock number" to each lock, and failing a
lock request for a lock with a lower number than that already
held is a design pattern that has been around since 1980 (in
Burroughs mainframes it was implemented in hardware). Easy
enough to do prior to C++17 in software.
Thats something else entirely.
And your assertion that a language that doesn't support it
intrinsically is "useless" is ridiculous.
Not useless then, just less useful.
I never ever used what you call "3 level locking", not even byStill don't really know what he means by 3 level locking. Using lock
mistake. But then, I don't write complicated apps on "big"
computers day in day out.
hashing where an address is hashed into a lock index such that no
object needs its own lock is nothing new. But it needs to be sorted
and deduped.
On Mon, 26 Oct 2026 13:12:24 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote:
On 10/26/2026 12:45 PM, Michael S wrote:
On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)Still don't really know what he means by 3 level locking. Using lock
boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 14:41:54 GMT
scott@slp53.sl.home (Scott Lurndal) gabbled:
boltar@caprica.universe writes:
C++ threading didn't have 3 level locking until 2017 making it
effectively useless IMO. Perhaps that was down to the lowest
common denominator called Windows.
Mind defining your terminology? "3 level locking", in
particular?
If you have to ask....
1. No lock
2. Write lock - Read only access, writer blocked until all readers
out of critic al section)
3. Read-write lock - all threads other than the one in section
block)
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11.
https://learn.microsoft.com/en-us/windows/win32/sync/slim-reader-writer--srw--locks
Of course WinXP remained popular for few more years, approximately
up until 2nd half of 2010, but that too predates publication of
C++11 in 2011-09.
This is basic stuff FFS. C++ finally got around to #2 with
shared_mutex in 2017 and its rather critical for certain
algorithms.
Assigning a canonical "lock number" to each lock, and failing a
lock request for a lock with a lower number than that already
held is a design pattern that has been around since 1980 (in
Burroughs mainframes it was implemented in hardware). Easy
enough to do prior to C++17 in software.
Thats something else entirely.
And your assertion that a language that doesn't support it
intrinsically is "useless" is ridiculous.
Not useless then, just less useful.
I never ever used what you call "3 level locking", not even by
mistake. But then, I don't write complicated apps on "big"
computers day in day out.
hashing where an address is hashed into a lock index such that no
object needs its own lock is nothing new. But it needs to be sorted
and deduped.
He explained it in the post above.
It seem that he mistyped few things in explanation, but it is possible
to understand intentions. He is talking about std::shared_mutex.
On 10/23/26 01:01, boltar@caprica.universe wrote:
On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bd7tj$rh4f$1@dont-email.me>,-a <boltar@battlestar.co.uk>
wrote:
Most of us have a CS degree. But then we go out into the real world,
get a
job and find out what real programming on real products entails, not
a load
of virtual academic naval gazing.
That's because it's not a trade school degree.-a It's not there to teach >>> you to program, it's there to teach you the fundamentals that you
need to
properly understand programming.
No, it teaches you fundamentals of certain aspects of computer
paradigms such
as databases, graphics, AI. Most people into computers learn actual
programming
long before they hit university.
Engineering schools are even more that way.-a They don't teach you much
engineering, but they give you all the background that you need to learn >>> engineering.
Programming isn't pure engineering - its a combination of engineering,
logic,
art and a trade.
If you just want a job, getting one of these degrees is not for you.
It's
not there for that.
Bill Gates never earned a degree. He seemed to do ok.
From what I understand, he wasn't a very good programmer, though.
Michael S <already5chosen@yahoo.com> writes:
On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
- Dan C.
First, he was talking about C++. Unlike me, he does not appear to care
about C.
Second, while in theory threads can be implemented by C++
compilers+language support library, in practice I had never seen it
done. All I had seen is C++ threads implemented in library as thin
wrapper atop of the OS (or RT executive) implementation.
I can not see while the same can't be done for processes, with
API modeled on posix_spawn() or Windows CreateProcess().
It does not look like variety in this field is bigger than in case of
threads. More like it is smaller.
Now, would it be the first thing I would want like addition to C++
standard library? No it would not be.
The first thing would be IPv4 communication, sockets, poll etc...
For which we, thankfully, have POSIX on most non-windows operating
systems.
On Mon, 26 Oct 2026 10:01:55 -0000 (UTC)Seems so! Damn it.
boltar@caprica.universe wrote:
On Sun, 25 Oct 2026 14:19:14 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/25/2026 1:34 AM, boltar@caprica.universe wrote:
On Sat, 24 Oct 2026 13:57:02 -0400 (EDT)
kludge@panix.com (Scott Dorsey) gabbled:
In article <11bif5s$2pam0$1@dont-email.me>,
Peter Flass <Peter@Iron-Spring.com> wrote:
You can have co-operative threads. IBM CICS used to run lots of
threads (tasks) concurrently, and ran them well.
When I learned C, there was no threading and there were only
different processes, so you had to do a fork and then synchronize
with the other process. This wasn't a dealbreaker and we did
plenty of stuff that way, but having threads available was very
nice and made for many operations becoming more convenient to
write.
Unfortunately most win32 programmers don't really understand
multiprocess programming because the w32 API is so borked so use
threads even when seperate process would be more appropriate.
Windows has what we need to run multi process. Even for a Mutex...
Remember WAIT_ABANDONED?
win32 can't do fork() making it effectively a totally useless API for
a lot of multiprocess development. Creating a brand new process is
fine if you don't need any complicated shared state such as when
kicking off something on the command line or creating a pipe
(something else win32 is shit at) but thats about it.
You are clueless about Windows. That's o.k.
Your pretense that you know something about it is not o.k.
In that regard you are not better than LDO.
On 25/10/2026 00:11, Michael S wrote:
On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <11bj08r$309uk$1@dont-email.me>,
Peter Flass-a <Peter@Iron-Spring.com> wrote:
On 10/24/26 09:41, Dan Cross wrote:
In article <11bhppd$2lpkc$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bf4d1$skul$1@dont-email.me>,
<boltar@caprica.universe> wrote:
On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bd7rg$2cvfs$1@dont-email.me>,
<boltar@battlestar.co.uk> wrote:
You need an OS to do threading properly too. Theres a reason >>>>>>>>>> green threads in java were a joke.
Weird that you think you need a operating system for threads, >>>>>>>>> yet you want C to standardize processes which also ... need an >>>>>>>>> operating system.-a I mean, POSIX already does an ok job of
standardizing the sorts of process-y things you would expect >>>>>>>>> from, you know, an operating system.
I'm simply pointing out the inconsistency in having a threading >>>>>>>> library but not a process library. Its perfectly possible to
simulate a multiprocess enviroment.
So write a simulator in your language of choice.-a You don't need >>>>>>> the language to standardize a process model for that.
Ditto threads. So why does C++ have a threading library?
Take your time...
What, pray tell, do you think that a _thread_ is?-a And how is it
different from a _process_?-a For that matter, what do you think
that a _process_ is?
Please, take all the time you need to answer.
Threads share resources such as address space, files, etc. A process
runs in its own address space. (at least these days, before virtual
memory, who knows?)
Indeed, but I'm hoping Mr Boltar will chime in with his answers,
so that we can understand why thinks that a language like C
should introduce a *process* model, and how threads are similar.
-a-a-a-a- Dan C.
First, he was talking about C++. Unlike me, he does not appear to care
about C.
Second, while in theory threads can be implemented by C++
compilers+language-a support library, in practice I had never seen it
done. All I had seen is C++ threads implemented in library as thin
wrapper atop of the OS (or RT executive) implementation.
I can not see while the same can't be done for processes, with
API modeled on posix_spawn() or Windows CreateProcess().
It does not look like variety in this field is bigger than in case of
threads. More like it is smaller.
No one is suggesting that the threads themselves are implemented in
pure, standard, portable C++.-a You need an underlying OS or support of
some sort if you are going to have preemptable threads.-a It's the same principle as IO and file access.
But the difference between threads and processes is very simple from the viewpoint of C and C++.-a Suppose you have a global (i.e., external
linkage) variable :
-a-a-a-aint x;
Two threads that have "int a = x;" see the same "x" (ignoring data races
and synchronisation).-a Two processes see completely different "x".[...]
On 10/25/2026 2:45 AM, David Brown wrote:
No one is suggesting that the threads themselves are implemented in
pure, standard, portable C++.-a You need an underlying OS or support of
some sort if you are going to have preemptable threads.-a It's the same
principle as IO and file access.
But the difference between threads and processes is very simple from
the viewpoint of C and C++.-a Suppose you have a global (i.e., external
linkage) variable :
-a-a-a-a-aint x;
Two threads that have "int a = x;" see the same "x" (ignoring data
races and synchronisation).-a Two processes see completely different
"x".[...]
Bingo. So, trying to imply that system is something okay for multi
process, well, good luck. Daft. C/C++ has no std way to deal with multi process. But, we can use C/C++ to program for it all day long. Interesting.
On 27/10/2026 04:44, Chris M. Thomasson wrote:
On 10/25/2026 2:45 AM, David Brown wrote:
No one is suggesting that the threads themselves are implemented
in pure, standard, portable C++.a You need an underlying OS or
support of some sort if you are going to have preemptable threads.
It's the same principle as IO and file access.
But the difference between threads and processes is very simple
from the viewpoint of C and C++.a Suppose you have a global (i.e.,
external linkage) variable :
aaaaaint x;
Two threads that have "int a = x;" see the same "x" (ignoring data
races and synchronisation).a Two processes see completely
different "x".[...]
Bingo. So, trying to imply that system is something okay for multi process, well, good luck. Daft. C/C++ has no std way to deal with
multi process. But, we can use C/C++ to program for it all day
long. Interesting.
There are, of course, languages and runtime systems that handle
processes too. An obvious example is Python. But it does it using a significantly "thicker" abstraction layer, combined with a
significant run-time system to manage it all. And as a programmer,
you have to be aware that you can't access global data from different processes, in the way you can do from different threads - you can
only use data that is explicitly shared, or of appropriate data
structures (like the process-aware queues). Behind the scenes, there
is a lot of work to pass and synchronise all this using named pipes, memmapped shared files, etc. While C++ programmers are used to there
being a certain degree of "hidden work" (unlike in C, where work is
much more explicit), this kind of thing is not at all a match for the
C++ philosophy.
And there are languages like Erlang that divide everything into micro-processes, and use the same mechanisms for controlling and
passing data around regardless of whether this little processes are
in the same thread, or different threads, different OS processes, or different computers. That works because there are very narrow and
tightly controlled mechanisms for sharing data.
Note that these are both languages that run on a VM, not compiled
languages.
boltar@caprica.universe wrote:
On Sun, 25 Oct 2026 14:22:34 -0700Basically that methinks you insult too much. Your wisdom here isn't
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
The differences are utterly irrelevant when it comes to prividing a
common
API to the functionality but thank you for demonstrating you had no
answer
to my question.
Ummm... It is relevant. Every process has a single thread of
execution, but not all processes have multiple threads.
No shit sherlock, thanks for the heads up. Your point is?
worth a sack of beans. I haven't learned one thing from you.
On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 14:41:54 GMT
scott@slp53.sl.home (Scott Lurndal) gabbled:
boltar@caprica.universe writes:
C++ threading didn't have 3 level locking until 2017 making it
effectively useless IMO. Perhaps that was down to the lowest common
denominator called Windows.
Mind defining your terminology? "3 level locking", in particular?
If you have to ask....
1. No lock
2. Write lock - Read only access, writer blocked until all readers
out of critic al section)
3. Read-write lock - all threads other than the one in section block)
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11.
Not useless then, just less useful.
I never ever used what you call "3 level locking", not even by mistake.
But then, I don't write complicated apps on "big" computers day in day
out.
On 10/26/2026 3:01 AM, boltar@caprica.universe wrote:
Creating a brand new process is fine if
you don't need any complicated shared state such as when kicking off
something
on the command line or creating a pipe (something else win32 is shit at)
but
thats about it.
Shared state? Just use memory mapped files. You don't need pipes/sockets >etc. You need to know how to properly sync things.
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
The problem with system() is not that. Often not even an efficiency.
The problem with system() identified most easily if we ask ourself "Why
do we want xyz in standard library?"
On Mon, 26 Oct 2026 10:01:55 -0000 (UTC)
boltar@caprica.universe wrote:
win32 can't do fork() making it effectively a totally useless API for
a lot of multiprocess development. Creating a brand new process is
fine if you don't need any complicated shared state such as when
kicking off something on the command line or creating a pipe
(something else win32 is shit at) but thats about it.
You are clueless about Windows. That's o.k.
Your pretense that you know something about it is not o.k.
In that regard you are not better than LDO.
On Mon, 26 Oct 2026 13:10:46 -0600
Blaine <cactus_DAC@yahoo.com> gabbled:
boltar@caprica.universe wrote:
On Sun, 25 Oct 2026 14:22:34 -0700Basically that methinks you insult too much. Your wisdom here isn't
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
The differences are utterly irrelevant when it comes to prividing a >>>>> common
API to the functionality but thank you for demonstrating you had no >>>>> answer
to my question.
Ummm... It is relevant. Every process has a single thread of
execution, but not all processes have multiple threads.
No shit sherlock, thanks for the heads up. Your point is?
worth a sack of beans. I haven't learned one thing from you.
Thats your problem, not mine.
On Mon, 26 Oct 2026 13:03:25 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/26/2026 3:01 AM, boltar@caprica.universe wrote:
Creating a brand new process is fine if
you don't need any complicated shared state such as when kicking off
something
on the command line or creating a pipe (something else win32 is shit
at) but
thats about it.
Shared state? Just use memory mapped files. You don't need
pipes/sockets etc. You need to know how to properly sync things.
Oh really? So you receive an incoming connection to a socket via an
accept()
call. In unix you can fork() at that point so the connecting client has a server process all to itself with all the state instantly copied from the parent process. HOw do you mimic that in windows? Start the server process from scratch and pass it a ton of state via the command line or using some roll-your-own shared memory nonsense? Give me a break. I guess in
windows it
spawns a thread leading to the issue of a single thread crashing
bringing down
the entire application - something multiprocess completely avoids.
On Mon, 26 Oct 2026 22:04:33 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
Rubbish, you clearly didn't bother to spend 2 mins googling.
The problem with system() is not that. Often not even an efficiency.
The problem with system() identified most easily if we ask ourself
"Why do we want xyz in standard library?"
The problem with system is its fire and forget - all you can do with
it is collect its exit code when its done. You can't communicate with
it via pipes, you can't control it via signals (well, not easily),
you can't set its process group, tty and on and on.
Oh, and it also
fires up the default shell to do the actual execution making it
hideously inefficient.
No serious unix dev uses system() unless thay
have absolutely no choice or it really is a case of "go run this, I
don't care what happens".
On Mon, 26 Oct 2026 22:09:01 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 10:01:55 -0000 (UTC)
boltar@caprica.universe wrote:
win32 can't do fork() making it effectively a totally useless API
for a lot of multiprocess development. Creating a brand new
process is fine if you don't need any complicated shared state
such as when kicking off something on the command line or creating
a pipe (something else win32 is shit at) but thats about it.
You are clueless about Windows. That's o.k.
Your pretense that you know something about it is not o.k.
In that regard you are not better than LDO.
OK, whats the windows API call thats the equivalent of fork()? I'm not talking about CreateProcessA() which doesn't even come close.
On Mon, 26 Oct 2026 13:03:25 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/26/2026 3:01 AM, boltar@caprica.universe wrote:
Creating a brand new process is fine if
you don't need any complicated shared state such as when kicking off
something
on the command line or creating a pipe (something else win32 is shit
at) but
thats about it.
Shared state? Just use memory mapped files. You don't need pipes/
sockets etc. You need to know how to properly sync things.
Oh really? So you receive an incoming connection to a socket via an
accept()
call. In unix you can fork() at that point so the connecting client has a server process all to itself with all the state instantly copied from the parent process. HOw do you mimic that in windows? Start the server process from scratch and pass it a ton of state via the command line or using some roll-your-own shared memory nonsense? Give me a break. I guess in
windows it
spawns a thread leading to the issue of a single thread crashing
bringing down
the entire application - something multiprocess completely avoids.
On Mon, 26 Oct 2026 21:45:17 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 14:41:54 GMT
scott@slp53.sl.home (Scott Lurndal) gabbled:
boltar@caprica.universe writes:
C++ threading didn't have 3 level locking until 2017 making it
effectively useless IMO. Perhaps that was down to the lowest common
denominator called Windows.
Mind defining your terminology? "3 level locking", in particular?
If you have to ask....
1. No lock
2. Write lock - Read only access, writer blocked until all readers
out of critic al section)
3. Read-write lock - all threads other than the one in section block)
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11.
And unix got pthreads in 1995. Windows a decade late as usual.
Not useless then, just less useful.
I never ever used what you call "3 level locking", not even by mistake.
But then, I don't write complicated apps on "big" computers day in day
out.
Fine, most people will never use it, but for certain things its vital.
On 10/28/2026 1:58 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 21:45:17 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 14:41:54 GMT
scott@slp53.sl.home (Scott Lurndal) gabbled:
boltar@caprica.universe writes:If you have to ask....
C++ threading didn't have 3 level locking until 2017 making it
effectively useless IMO. Perhaps that was down to the lowest common >>>>>> denominator called Windows.
Mind defining your terminology?-a-a "3 level locking", in particular? >>>>
1. No lock
2. Write lock - Read only access, writer blocked until all readers
out of critic al section)
3. Read-write lock-a - all threads other than the one in section block) >>>>
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11.
And unix got pthreads in 1995. Windows a decade late as usual.
Not useless then, just less useful.
I never ever used what you call "3 level locking", not even by mistake.
But then, I don't write complicated apps on "big" computers day in day
out.
Fine, most people will never use it, but for certain things its vital.
Its simple, if you don't like windows, do use the damn pile.
On Mon, 26 Oct 2026 22:04:33 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
Rubbish, you clearly didn't bother to spend 2 mins googling.
The problem with system() is not that. Often not even an efficiency.
The problem with system() identified most easily if we ask ourself "Why
do we want xyz in standard library?"
The problem with system is its fire and forget - all you can do with it is collect its exit code when its done. You can't communicate with it via
pipes, you can't control it via signals (well, not easily), you can't set its process group, tty and on and on. Oh, and it also fires up the default shell to
do the actual execution making it hideously inefficient. No serious unix dev uses system() unless thay have absolutely no choice or it really is a case of "go run this, I don't care what happens".
On Mon, 26 Oct 2026 21:45:17 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 14:41:54 GMT
scott@slp53.sl.home (Scott Lurndal) gabbled:
boltar@caprica.universe writes:
C++ threading didn't have 3 level locking until 2017 making it
effectively useless IMO. Perhaps that was down to the lowest
common denominator called Windows.
Mind defining your terminology? "3 level locking", in
particular?
If you have to ask....
1. No lock
2. Write lock - Read only access, writer blocked until all readers
out of critic al section)
3. Read-write lock - all threads other than the one in section
block)
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11.
And unix got pthreads in 1995. Windows a decade late as usual.
On Wed, 28 Oct 2026 09:08:44 -0000 (UTC)
boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 22:09:01 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 10:01:55 -0000 (UTC)
boltar@caprica.universe wrote:
win32 can't do fork() making it effectively a totally useless API
for a lot of multiprocess development. Creating a brand new
process is fine if you don't need any complicated shared state
such as when kicking off something on the command line or creating
a pipe (something else win32 is shit at) but thats about it.
You are clueless about Windows. That's o.k.
Your pretense that you know something about it is not o.k.
In that regard you are not better than LDO.
OK, whats the windows API call thats the equivalent of fork()? I'm not
talking about CreateProcessA() which doesn't even come close.
There is no equivalent for fork(). But nearly all things that Posix
devs achieve by fork() followed by one or another magic incantation and
then followed by exec() can be achived on Windows as well, typically by
means of one or another magic flag in parameters of CreateProcess or
of one of it's more complicated cousins (CreateProcessAsUser, >CreateProcessWithLogon, CreateProcessWithToken, may be others). These
things never fascinated me, so I am not an expert.
Now, there were cases where Unix programmers used fork() without
following it by exec(), but I would think that in the recent 25-30 years
such programming patterns are discouraged in favor of threads.
On 10/28/2026 2:01 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 13:03:25 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/26/2026 3:01 AM, boltar@caprica.universe wrote:
Creating a brand new process is fine if
you don't need any complicated shared state such as when kicking off
something
on the command line or creating a pipe (something else win32 is shit
at) but
thats about it.
Shared state? Just use memory mapped files. You don't need pipes/
sockets etc. You need to know how to properly sync things.
Oh really? So you receive an incoming connection to a socket via an
accept()
call. In unix you can fork() at that point so the connecting client has a
server process all to itself with all the state instantly copied from the
parent process. HOw do you mimic that in windows? Start the server process >> from scratch and pass it a ton of state via the command line or using some >> roll-your-own shared memory nonsense? Give me a break. I guess in
windows it
spawns a thread leading to the issue of a single thread crashing
bringing down
the entire application - something multiprocess completely avoids.
On Windows? Get used to
https://learn.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-wsadup
licatesocketa
DuplicateHandle
On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 22:04:33 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
Rubbish, you clearly didn't bother to spend 2 mins googling.
The problem with system() is not that. Often not even an efficiency.
The problem with system() identified most easily if we ask ourself "Why
do we want xyz in standard library?"
The problem with system is its fire and forget - all you can do with it is >> collect its exit code when its done. You can't communicate with it via
pipes, you can't control it via signals (well, not easily), you can't set its
process group, tty and on and on. Oh, and it also fires up the default shell >to
do the actual execution making it hideously inefficient. No serious unix dev >> uses system() unless thay have absolutely no choice or it really is a case of
"go run this, I don't care what happens".
Right. std::system, at least when I use it, makes the caller block until
the process is done.
On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
boltar@caprica.universe wrote:
And unix got pthreads in 1995. Windows a decade late as usual.
That's like if I'd say that Linux is 33 years (and counting) late
because it has no QueueUserAPC(). Of course, I am smarter than saying
such nonsense.
More relevantly, Windows (Win32) has preemptive kernel-scheduled threads
+ assortment of synchronization primitives since very beginning (1993)
- ahead of many Unixen and behind some of them. Certainly ahead of
Posix standardisation of threads.
On Wed, 28 Oct 2026 14:04:02 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/28/2026 2:01 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 13:03:25 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/26/2026 3:01 AM, boltar@caprica.universe wrote:
Creating a brand new process is fine if
you don't need any complicated shared state such as when kicking
off something
on the command line or creating a pipe (something else win32 is
shit at) but
thats about it.
Shared state? Just use memory mapped files. You don't need pipes/
sockets etc. You need to know how to properly sync things.
Oh really? So you receive an incoming connection to a socket via an
accept()
call. In unix you can fork() at that point so the connecting client
has a
server process all to itself with all the state instantly copied from
the
parent process. HOw do you mimic that in windows? Start the server
process
from scratch and pass it a ton of state via the command line or using
some
roll-your-own shared memory nonsense? Give me a break. I guess in
windows it
spawns a thread leading to the issue of a single thread crashing
bringing down
the entire application - something multiprocess completely avoids.
On Windows? Get used to
https://learn.microsoft.com/en-us/windows/win32/api/winsock2/nf-
winsock2-wsadup
licatesocketa
DuplicateHandle
Right, lets duplicate everything manually - so much easier than one
system call.
And thats just file descriptors.
On Thu, 29 Oct 2026 00:06:45 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
boltar@caprica.universe wrote:
And unix got pthreads in 1995. Windows a decade late as usual.
That's like if I'd say that Linux is 33 years (and counting) late
because it has no QueueUserAPC(). Of course, I am smarter than saying
such nonsense.
More relevantly, Windows (Win32) has preemptive kernel-scheduled
threads
+ assortment of synchronization primitives since very beginning
(1993)
- ahead of many Unixen and behind some of them. Certainly ahead of
Posix standardisation of threads.
Wow, pre-emptive multitasking in 1993. Incredible technology!
On Wed, 28 Oct 2026 14:09:32 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 22:04:33 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
Rubbish, you clearly didn't bother to spend 2 mins googling.
The problem with system() is not that. Often not even an
efficiency. The problem with system() identified most easily if
we ask ourself "Why do we want xyz in standard library?"
The problem with system is its fire and forget - all you can do
with it is collect its exit code when its done. You can't
communicate with it via pipes, you can't control it via signals
(well, not easily), you can't set its
process group, tty and on and on. Oh, and it also fires up theto
default shell
do the actual execution making it hideously inefficient. No
serious unix dev uses system() unless thay have absolutely no
choice or it really is a case of
"go run this, I don't care what happens".
Right. std::system, at least when I use it, makes the caller block
until the process is done.
Thats true. Its been so long since I used it I'd forgotten about
that. Makes it even less useful.
On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
boltar@caprica.universe wrote:
On Thu, 29 Oct 2026 00:06:45 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
boltar@caprica.universe wrote:
And unix got pthreads in 1995. Windows a decade late as usual.
That's like if I'd say that Linux is 33 years (and counting) late
because it has no QueueUserAPC(). Of course, I am smarter than saying
such nonsense.
More relevantly, Windows (Win32) has preemptive kernel-scheduled
threads
+ assortment of synchronization primitives since very beginning
(1993)
- ahead of many Unixen and behind some of them. Certainly ahead of
Posix standardisation of threads.
Wow, pre-emptive multitasking in 1993. Incredible technology!
Not just preemptive multitasking between processes, but
kernel-scheduled threads within each process as well.
Not a novel idea, but the one that eventually won over all others.
In 1993 it was already obvious that it is going to win, but in
1988-1989, when development started, it was less trivial.
On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
boltar@caprica.universe wrote:
On Thu, 29 Oct 2026 00:06:45 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
boltar@caprica.universe wrote:
And unix got pthreads in 1995. Windows a decade late as usual.
That's like if I'd say that Linux is 33 years (and counting) late
because it has no QueueUserAPC(). Of course, I am smarter than saying
such nonsense.
More relevantly, Windows (Win32) has preemptive kernel-scheduled
threads
+ assortment of synchronization primitives since very beginning
(1993)
- ahead of many Unixen and behind some of them. Certainly ahead of
Posix standardisation of threads.
Wow, pre-emptive multitasking in 1993. Incredible technology!
Not just preemptive multitasking between processes, but
kernel-scheduled threads within each process as well.
Not a novel idea, but the one that eventually won over all others.
In 1993 it was already obvious that it is going to win, but in
1988-1989, when development started, it was less trivial.
On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
boltar@caprica.universe wrote:
On Wed, 28 Oct 2026 14:09:32 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 22:04:33 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
Rubbish, you clearly didn't bother to spend 2 mins googling.
The problem with system() is not that. Often not even an
efficiency. The problem with system() identified most easily if
we ask ourself "Why do we want xyz in standard library?"
The problem with system is its fire and forget - all you can do
with it is collect its exit code when its done. You can't
communicate with it via pipes, you can't control it via signals
(well, not easily), you can't set its
process group, tty and on and on. Oh, and it also fires up theto
default shell
do the actual execution making it hideously inefficient. No
serious unix dev uses system() unless thay have absolutely no
choice or it really is a case of
"go run this, I don't care what happens".
Right. std::system, at least when I use it, makes the caller block
until the process is done.
Thats true. Its been so long since I used it I'd forgotten about
that. Makes it even less useful.
Does it block when your command processor is bash and your command
string is "my_subprocess &"?
Michael S <already5chosen@yahoo.com> writes:
On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
boltar@caprica.universe wrote:
On Wed, 28 Oct 2026 14:09:32 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 22:04:33 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
Rubbish, you clearly didn't bother to spend 2 mins googling.
The problem with system() is not that. Often not even an
efficiency. The problem with system() identified most easily if
we ask ourself "Why do we want xyz in standard library?"
The problem with system is its fire and forget - all you can do
with it is collect its exit code when its done. You can't
communicate with it via pipes, you can't control it via signals
(well, not easily), you can't set its
process group, tty and on and on. Oh, and it also fires up theto
default shell
do the actual execution making it hideously inefficient. No
serious unix dev uses system() unless thay have absolutely no
choice or it really is a case of
"go run this, I don't care what happens".
Right. std::system, at least when I use it, makes the caller block
until the process is done.
Thats true. Its been so long since I used it I'd forgotten about
that. Makes it even less useful.
Does it block when your command processor is bash and your command
string is "my_subprocess &"?
You might need to do 'nohup my_subprocess &' if my_subprocess
doesn't intercept SIGHUP.
Michael S <already5chosen@yahoo.com> writes:
On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
boltar@caprica.universe wrote:
On Thu, 29 Oct 2026 00:06:45 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
boltar@caprica.universe wrote:
And unix got pthreads in 1995. Windows a decade late as usual.
That's like if I'd say that Linux is 33 years (and counting) late
because it has no QueueUserAPC(). Of course, I am smarter than saying
such nonsense.
More relevantly, Windows (Win32) has preemptive kernel-scheduled
threads
+ assortment of synchronization primitives since very beginning
(1993)
- ahead of many Unixen and behind some of them. Certainly ahead of
Posix standardisation of threads.
Wow, pre-emptive multitasking in 1993. Incredible technology!
Not just preemptive multitasking between processes, but
kernel-scheduled threads within each process as well.
Not a novel idea, but the one that eventually won over all others.
In 1993 it was already obvious that it is going to win, but in
1988-1989, when development started, it was less trivial.
The thread design for SVR4 Unix started in the late 80s and
released in 1993.
Digital published "Evolving the UNIX System Interface to
Support Multithreaded Programs" September 28, 1987.
(Paul R. McJones and Garret F. Swart).
The "The Topaz Operating System User's Guide" in that document
describes the thread interface. (DIGITAL Systems Research
Center operating system) for both VAX/Ultrix and the Firefly/Taos >implementation.
Here's a link to the paper published a couple years later:
https://softwarepreservation.computerhistory.org/modula2+/doc/McJones_Swart-Evolving-1989.pdf
And here's a link to the full technical report #21 (including the manual)
https://ftp.zx.net.nz/pub/archive/gatekeeper.dec.com/pub/DEC/SRC/research-reports/SRC-021.pdf
On Thu, 29 Oct 2026 22:26:40 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:
Michael S <already5chosen@yahoo.com> writes:
On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
boltar@caprica.universe wrote:
On Wed, 28 Oct 2026 14:09:32 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 22:04:33 +0200to
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
Rubbish, you clearly didn't bother to spend 2 mins googling.
The problem with system() is not that. Often not even an
efficiency. The problem with system() identified most easily if
we ask ourself "Why do we want xyz in standard library?"
The problem with system is its fire and forget - all you can do
with it is collect its exit code when its done. You can't
communicate with it via pipes, you can't control it via signals
(well, not easily), you can't set its
process group, tty and on and on. Oh, and it also fires up the
default shell
do the actual execution making it hideously inefficient. No
serious unix dev uses system() unless thay have absolutely no
choice or it really is a case of
"go run this, I don't care what happens".
Right. std::system, at least when I use it, makes the caller block
until the process is done.
Thats true. Its been so long since I used it I'd forgotten about
that. Makes it even less useful.
Does it block when your command processor is bash and your command
string is "my_subprocess &"?
You might need to do 'nohup my_subprocess &' if my_subprocess
doesn't intercept SIGHUP.
You are likely right. Otherwise OS will kill my_subprocess at about the
same time the caller of system() gets control back.
I would not figure it out myself.
In article <20261030005434.00005458@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Thu, 29 Oct 2026 22:26:40 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:
Michael S <already5chosen@yahoo.com> writes:
On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
boltar@caprica.universe wrote:
On Wed, 28 Oct 2026 14:09:32 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
On Mon, 26 Oct 2026 22:04:33 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
boltar@caprica.universe wrote:
Go ahead and remain clueless.
system() can do most of the same things as spawn() family.
Rubbish, you clearly didn't bother to spend 2 mins googling.
The problem with system() is not that. Often not even an
efficiency. The problem with system() identified most
easily if we ask ourself "Why do we want xyz in standard
library?"
The problem with system is its fire and forget - all you can
do with it is collect its exit code when its done. You can't
communicate with it via pipes, you can't control it via
signals (well, not easily), you can't set its
process group, tty and on and on. Oh, and it also fires upto
the default shell
do the actual execution making it hideously inefficient. No
serious unix dev uses system() unless thay have absolutely no
choice or it really is a case of
"go run this, I don't care what happens".
Right. std::system, at least when I use it, makes the caller
block until the process is done.
Thats true. Its been so long since I used it I'd forgotten about
that. Makes it even less useful.
Does it block when your command processor is bash and your command
string is "my_subprocess &"?
You might need to do 'nohup my_subprocess &' if my_subprocess
doesn't intercept SIGHUP.
You are likely right. Otherwise OS will kill my_subprocess at about
the same time the caller of system() gets control back.
I would not figure it out myself.
Only if you intended to close the TTY the programs were started
on. Otherwise, I don't see why it would be necessary:
```
term% cat a.c
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
#include <unistd.h>
int
main(void)
{
struct tm *t;
time_t now = time(NULL);
printf("Starting child, time is %s", asctime(gmtime(&now)));
sleep(5);
now = time(NULL);
printf("Bye bye, now is %s", asctime(gmtime(&now)));
}
term% cat b.c
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
#include <unistd.h>
int
main(void)
{
time_t now = time(NULL);
printf("Parent starting, time is %s", asctime(gmtime(&now)));
system("./a &");
printf("./a started in background\n");
sleep(2);
now = time(NULL);
printf("Ahhh!!! time is %s", asctime(gmtime(&now)));
return 0;
}
term% make a
cc -O2 -pipe -o a a.c
term% make b
cc -O2 -pipe -o b b.c
term% ./b
Parent starting, time is Fri Oct 30 02:21:06 2026
./a started in background
Starting child, time is Fri Oct 30 02:21:06 2026
Ahhh!!! time is Fri Oct 30 02:21:08 2026
term% Bye bye, now is Fri Oct 30 02:21:11 2026
```
- Dan C.
On 10/29/2026 9:19 AM, boltar@caprica.universe wrote:
Right, lets duplicate everything manually - so much easier than one
system call.
And thats just file descriptors.
Do we actually need everything, or just a subset?
On Fri, 30 Oct 2026 02:22:43 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261030005434.00005458@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Thu, 29 Oct 2026 22:26:40 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:
Michael S <already5chosen@yahoo.com> writes:
On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
[snip]
Does it block when your command processor is bash and your command
string is "my_subprocess &"?
You might need to do 'nohup my_subprocess &' if my_subprocess
doesn't intercept SIGHUP.
You are likely right. Otherwise OS will kill my_subprocess at about
the same time the caller of system() gets control back.
I would not figure it out myself.
Only if you intended to close the TTY the programs were started
on. Otherwise, I don't see why it would be necessary:
What happens when caller is GUI-style application?
--- Synchronet 3.22a-Linux NewsLink 1.2```
term% cat a.c
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
#include <unistd.h>
int
main(void)
{
time_t now = time(NULL);
printf("Starting child, time is %s", asctime(gmtime(&now)));
sleep(5);
now = time(NULL);
printf("Bye bye, now is %s", asctime(gmtime(&now)));
}
term% cat b.c
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
#include <unistd.h>
int
main(void)
{
time_t now = time(NULL);
printf("Parent starting, time is %s", asctime(gmtime(&now)));
system("./a &");
printf("./a started in background\n");
sleep(2);
now = time(NULL);
printf("Ahhh!!! time is %s", asctime(gmtime(&now)));
return 0;
}
term% make a
cc -O2 -pipe -o a a.c
term% make b
cc -O2 -pipe -o b b.c
term% ./b
Parent starting, time is Fri Oct 30 02:21:06 2026
./a started in background
Starting child, time is Fri Oct 30 02:21:06 2026
Ahhh!!! time is Fri Oct 30 02:21:08 2026
term% Bye bye, now is Fri Oct 30 02:21:11 2026
```
On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
boltar@caprica.universe wrote:
On Thu, 29 Oct 2026 00:06:45 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
boltar@caprica.universe wrote:
And unix got pthreads in 1995. Windows a decade late as usual.
That's like if I'd say that Linux is 33 years (and counting) late
because it has no QueueUserAPC(). Of course, I am smarter than saying
such nonsense.
More relevantly, Windows (Win32) has preemptive kernel-scheduled
threads
+ assortment of synchronization primitives since very beginning
(1993)
- ahead of many Unixen and behind some of them. Certainly ahead of
Posix standardisation of threads.
Wow, pre-emptive multitasking in 1993. Incredible technology!
Not just preemptive multitasking between processes, but
kernel-scheduled threads within each process as well.
Not a novel idea, but the one that eventually won over all others.
In 1993 it was already obvious that it is going to win, but in
1988-1989, when development started, it was less trivial.
The OS will not kill your program when the shell started by
`system` exits or anything;
nor will the shell itself.
In article <20261030105900.000020ce@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
Only if you intended to close the TTY the programs were started
on. Otherwise, I don't see why it would be necessary:
What happens when caller is GUI-style application?
That depends on a number of factors, but basically, "it does the
same thing". Why would it be any different?
On Thu, 29 Oct 2026 22:39:22 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
boltar@caprica.universe wrote:
On Thu, 29 Oct 2026 00:06:45 +0200
Michael S <already5chosen@yahoo.com> gabbled:
On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
boltar@caprica.universe wrote:
And unix got pthreads in 1995. Windows a decade late as usual.
That's like if I'd say that Linux is 33 years (and counting) late
because it has no QueueUserAPC(). Of course, I am smarter than saying
such nonsense.
More relevantly, Windows (Win32) has preemptive kernel-scheduled
threads
+ assortment of synchronization primitives since very beginning
(1993)
- ahead of many Unixen and behind some of them. Certainly ahead of
Posix standardisation of threads.
Wow, pre-emptive multitasking in 1993. Incredible technology!
Not just preemptive multitasking between processes, but
kernel-scheduled threads within each process as well.
Not a novel idea, but the one that eventually won over all others.
In 1993 it was already obvious that it is going to win, but in
1988-1989, when development started, it was less trivial.
Implementing threads is trivial compared to implementing multi processes with shared memory. Adding them to a pre-existing kernel might be tricky but when you're building one from scratch as per NT then its hardly a big deal.
On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261030105900.000020ce@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
Only if you intended to close the TTY the programs were started
on. Otherwise, I don't see why it would be necessary:
What happens when caller is GUI-style application?
That depends on a number of factors, but basically, "it does the
same thing". Why would it be any different?
Windows treats GUI apps entirely differently to console ones so a Windows
dev might not appreciate that on unix there is no demarcation - a GUI app simply has a network connection to the X server and it can either sit in
an event loop waiting for events - as per a windows main thread - or go do other things and periodically check the X event list.
On 10/30/26 17:07, boltar@caprica.universe wrote:
On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261030105900.000020ce@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
Only if you intended to close the TTY the programs were started
on. Otherwise, I don't see why it would be necessary:
What happens when caller is GUI-style application?
That depends on a number of factors, but basically, "it does the
same thing". Why would it be any different?
Windows treats GUI apps entirely differently to console ones so a Windows
dev might not appreciate that on unix there is no demarcation - a GUI app
simply has a network connection to the X server and it can either sit in
an event loop waiting for events - as per a windows main thread - or go do >> other things and periodically check the X event list.
That's where threads are useful: The GUI is one thread, and the "other >things" are in one or more other threads. There are altogether too many >programs that hang the GUI while "other things" are going on. That
should never happen!
On 10/24/2026 11:12 AM, Titus G wrote:
Why does Mozilla Firefox update itself just about every week?
There was an emergency Firefox update a few days ago, I believe, because
of the e-something-or-other in India screwed up root key generation for
their certificate authority. You can read the details at Ars Technica
or elsewhere.
https://arstechnica.com/security/2026/10/disgraced-emudhra-drops-out-of-tls-business-following-certificate-debacle/
One of the keys was literally 4, according to the article. I wonder if
they threw a six sided die?
I cannot help with your Firefox account, other than say I am not using
one yet, so there may still be a way to bypass the need. However, I
cannot say how since I don't care about the Firefox user interface after
they started to move everything around all the time.
If you bring back Netscape 7 let me know.
Best wishes, and happy browser wars!--
On Fri, 30 Oct 2026 20:37:14 +0100
Jeroen Belleman <jeroen@nospam.please> gabbled:
On 10/30/26 17:07, boltar@caprica.universe wrote:
On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261030105900.000020ce@yahoo.com>,
Michael S-a <already5chosen@yahoo.com> wrote:
Only if you intended to close the TTY the programs were started
on.-a Otherwise, I don't see why it would be necessary:
What happens when caller is GUI-style application?
That depends on a number of factors, but basically, "it does the
same thing".-a Why would it be any different?
Windows treats GUI apps entirely differently to console ones so a
Windows
dev might not appreciate that on unix there is no demarcation - a GUI
app
simply has a network connection to the X server and it can either sit in >>> an event loop waiting for events - as per a windows main thread - or
go do
other things and periodically check the X event list.
That's where threads are useful: The GUI is one thread, and the "other
things" are in one or more other threads. There are altogether too many
programs that hang the GUI while "other things" are going on. That
should never happen!
If its multithreaded but that still happens someone probably has created
too
many critical sections with too many locks.
On Fri, 30 Oct 2026 20:37:14 +0100
Jeroen Belleman <jeroen@nospam.please> gabbled:
On 10/30/26 17:07, boltar@caprica.universe wrote:
On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261030105900.000020ce@yahoo.com>,
Michael S-a <already5chosen@yahoo.com> wrote:
Only if you intended to close the TTY the programs were started
on.-a Otherwise, I don't see why it would be necessary:
What happens when caller is GUI-style application?
That depends on a number of factors, but basically, "it does the
same thing".-a Why would it be any different?
Windows treats GUI apps entirely differently to console ones so a
Windows
dev might not appreciate that on unix there is no demarcation - a GUI
app
simply has a network connection to the X server and it can either sit in >>> an event loop waiting for events - as per a windows main thread - or
go do
other things and periodically check the X event list.
That's where threads are useful: The GUI is one thread, and the "other
things" are in one or more other threads. There are altogether too many
programs that hang the GUI while "other things" are going on. That
should never happen!
If its multithreaded but that still happens someone probably has created
too
many critical sections with too many locks.
On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
On Fri, 30 Oct 2026 20:37:14 +0100
Jeroen Belleman <jeroen@nospam.please> gabbled:
On 10/30/26 17:07, boltar@caprica.universe wrote:
On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261030105900.000020ce@yahoo.com>,
Michael S-a <already5chosen@yahoo.com> wrote:
Only if you intended to close the TTY the programs were started
on.-a Otherwise, I don't see why it would be necessary:
What happens when caller is GUI-style application?
That depends on a number of factors, but basically, "it does the
same thing".-a Why would it be any different?
Windows treats GUI apps entirely differently to console ones so a
Windows
dev might not appreciate that on unix there is no demarcation - a GUI >>>> app
simply has a network connection to the X server and it can either sit in >>>> an event loop waiting for events - as per a windows main thread - or
go do
other things and periodically check the X event list.
That's where threads are useful: The GUI is one thread, and the "other
things" are in one or more other threads. There are altogether too many
programs that hang the GUI while "other things" are going on. That
should never happen!
If its multithreaded but that still happens someone probably has created
too
many critical sections with too many locks.
What do you mean? Is the GUI deadlocking?
On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
If its multithreaded but that still happens someone probably has created
too
many critical sections with too many locks.
Makes no sense at all. Have you taken a look at my multex? It can create
a shit lod of mutexes, and never deadlock. It keeps a strict locking
order. Sorts and dedups the mutexes. Also, notice that an object does
not need its own mutex:
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11. https://learn.microsoft.com/en-us/windows/win32/sync/slim-reader- writer--srw--locks
Of course WinXP remained popular for few more years, approximately up
until 2nd half of 2010, but that too predates publication of C++11 in 2011-09.
On Sat, 31 Oct 2026 13:11:29 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
On Fri, 30 Oct 2026 20:37:14 +0100
Jeroen Belleman <jeroen@nospam.please> gabbled:
On 10/30/26 17:07, boltar@caprica.universe wrote:
On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <20261030105900.000020ce@yahoo.com>,
Michael S-a <already5chosen@yahoo.com> wrote:
Only if you intended to close the TTY the programs were started >>>>>>>> on.-a Otherwise, I don't see why it would be necessary:
What happens when caller is GUI-style application?
That depends on a number of factors, but basically, "it does the
same thing".-a Why would it be any different?
Windows treats GUI apps entirely differently to console ones so a
Windows
dev might not appreciate that on unix there is no demarcation - a
GUI app
simply has a network connection to the X server and it can either
sit in
an event loop waiting for events - as per a windows main thread -
or go do
other things and periodically check the X event list.
That's where threads are useful: The GUI is one thread, and the
"other things" are in one or more other threads. There are
altogether too many
programs that hang the GUI while "other things" are going on. That
should never happen!
If its multithreaded but that still happens someone probably has
created too
many critical sections with too many locks.
What do you mean? Is the GUI deadlocking?
What do I mean? If you don't understand the concepts of multithreading then maybe stay out of the discussion.
On Sat, 31 Oct 2026 13:14:47 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
If its multithreaded but that still happens someone probably has
created too
many critical sections with too many locks.
Makes no sense at all. Have you taken a look at my multex? It can create
WTF has your multex got to do with anything? No one was talking about your code so don't use this discussion as some excuse to show off some code you wrote than no one cares about.
a shit lod of mutexes, and never deadlock. It keeps a strict locking
order. Sorts and dedups the mutexes. Also, notice that an object does
not need its own mutex:
Thats nice.
tl;dr
rCLThe end of software secrecy is almost upon us. The death of closed source, and the final triumph of open source. rCY -Eric S. Raymond.I have provided Claude Code with snippets of coderCoroughly a screen's
-a-a https://www.battleswarmblog.com/?p=73639
"I should have realized this a few months ago when I successfully
decompiled the game of Firefighter from an ancient DOS shareware binary.
My robot friend was able to tell it had been written in Borland Pascal
from looking at the data layout; it gave me back very readable Pascal
code with sensibly chosen function and variable names. I transpiled it
to Rust and now ship it as part of my heritage games collection."
Huh, so somebody has actually built a decent decompiler.-a Why do I doubt this even though ESR says otherwise?
And he has a translator from Borland Pascal to Rust?
On 10/20/2026 2:22 PM, Scott Dorsey wrote:
In article <11b8b2k$p44i$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>> Cryptoengineer <petertrei@gmail.com> wrote:
Edgar Dijkstra: Go To Statement Considered Harmful
A man who clearly never programmed in assembler.
I have seen a structured assembler class and it's actually not a bad way
to think at all. Having LOOPZ and REP* and similar instructions make it
easier to think about do loops.
The key to writing structured assembly is commenting.
The key to writing [] assembly is commenting.
Fixed That For You.
pt
On 11/1/2026 1:33 AM, boltar@caprica.universe wrote:
What do you mean? Is the GUI deadlocking?
What do I mean? If you don't understand the concepts of multithreading then >> maybe stay out of the discussion.
Ummm. I think you are the one that does not know what the heck they are >talking about.
On 11/1/2026 1:34 AM, boltar@caprica.universe wrote:
On Sat, 31 Oct 2026 13:14:47 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:WTF has your multex got to do with anything? No one was talking about your >> code so don't use this discussion as some excuse to show off some code you >> wrote than no one cares about.
If its multithreaded but that still happens someone probably has
created too
many critical sections with too many locks.
Makes no sense at all. Have you taken a look at my multex? It can create >>
It uses a table of a lot of mutexes. Never deadlocks. So, you need to
study up? You said "too many critical sections with too many locks."
Well, if you don't know how to use them, don't use them. Learn first?
On Sun, 1 Nov 2026 18:04:13 -0800
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 11/1/2026 1:34 AM, boltar@caprica.universe wrote:
On Sat, 31 Oct 2026 13:14:47 -0700
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
If its multithreaded but that still happens someone probably has
created too
many critical sections with too many locks.
Makes no sense at all. Have you taken a look at my multex? It can
create
WTF has your multex got to do with anything? No one was talking about
your
code so don't use this discussion as some excuse to show off some
code you
wrote than no one cares about.
It uses a table of a lot of mutexes. Never deadlocks. So, you need to
study up? You said "too many critical sections with too many locks."
Well, if you don't know how to use them, don't use them. Learn first?
I have no desire to spend hours trawling through someones pet project so they
can make a point about what a L337 coder they are. HTH.
On Sun, 1 Nov 2026 18:03:06 -0800
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
On 11/1/2026 1:33 AM, boltar@caprica.universe wrote:
What do you mean? Is the GUI deadlocking?
What do I mean? If you don't understand the concepts of
multithreading then
maybe stay out of the discussion.
Ummm. I think you are the one that does not know what the heck they
are talking about.
Yeah, ok. I've only been using pthreads for the last 25 years but sure,
what
do I know.
On 10/27/2026 3:45 AM, Michael S wrote:
Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
time as conditional variables. 5 years before C++11.
https://learn.microsoft.com/en-us/windows/win32/sync/slim-reader-
writer--srw--locks
Of course WinXP remained popular for few more years, approximately up
until 2nd half of 2010, but that too predates publication of C++11 in
2011-09.
Wasn't that work done in preparation for the C++11 standard?-a I did not
keep track of the standard's discussion, but presumably Microsoft had
people both on the C++ standard's committee, and the Vista programming
team.
Best wishes, and happy standards!
For the particular case of why C++ supports threads but not processes,
the answer should be obvious.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 60:36:23 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 286,219 |