Re: Pre-main construction order in modules

On Tue, 1 Apr 2025 11:48:23 +0300
Paavo Helde <eesnimi@osa.pri.ee> wibbled:

On 01.04.2025 10:26, Muttley@DastardlyHQ.org wrote:

On Mon, 31 Mar 2025 19:42:48 -0400
James Kuyper <jameskuyper@alumni.caltech.edu> wibbled:

On 31.03.2025 17:01, Muttley@DastardlyHQ.org wrote:

On Mon, 31 Mar 2025 15:39:53 +0300
Paavo Helde <eesnimi@osa.pri.ee> wibbled:

On 31.03.2025 12:09, Muttley@DastardlyHQ.org wrote:
"If [initialization] is deferred, it strongly happens before any
non-initialization odr-use of any non-inline function or non-inline
variable defined in the same translation unit as the variable to be
initialized."

>
Who writes this stuff? Its borderline gibberish.

>
Keep in mind that the key thing that makes this seem like gibberish is
the use of precisely defined technical jargon, which is used for the
same reason that jargon is used in many other contexts: it has a more
precisely specified meaning than more informal wording would have had.
>
Key pieces of jargon: "strongly happens before", "non-initialization",

 
"strongly happens before" is genuine gibberish. Either something happens

before

or it doesn't, the adverb is entirely superfluous.

>
Welcome to the 21-st century where out-of-sync CPU caches and pipelines
are the norm.

Are you smoking something illegal? You're making less sense than that
paragraph.

I'm a native english speaker and had to read it more than once to understand
it.

>
Somehow I suspect you have not understood much. For understanding the
technical terms you need to read their definitions in the standard, not
try to guess their meaning by an isolated usage example.

Save your lame patronising for someone who cares and while you're at it
mene vittuun itseäsi.