Sujet : Re: Pre-main construction order in modules
De : Muttley (at) *nospam* DastardlyHQ.org
Groupes : comp.lang.c++Date : 02. Apr 2025, 08:34:52
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vsipas$199of$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10
On Tue, 1 Apr 2025 14:32:54 -0400
James Kuyper <
jameskuyper@alumni.caltech.edu> wibbled:
"An evaluation A strongly happens before an evaluation D if, either
:
(12.4)— there is an evaluation B such that A strongly happens before B,
and B strongly happens before D.
Looks like a circular definition to me. But regardless, looks like the usual
unintelligable nonsense thats no use to anyone except the people who wrote it.
Do you need an explanation of the parts of the above explanation that
use the terms "release" and "consume"? I have little experience with
multi-threaded code - someone else might be able to explain those better
than I can.
I don't particularly care. I generally find standards and RFCs unreadable.
Its often easier to look at code or test with a working example to see what
actually happens. Thats the method I used to write my NNTP and NMAP clients
amongst many others.