Re: Pre-main construction order in modules

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.
 

The keyword here is "non-initialization use". If you access your myobj
from main() it would be a non-initialization use, which is guaranteed to trigger the needed initialization if needed, so everything will work fine.

 Not necessarily. What it the constructor of one object opened a network
socket but that object wasn't touched again until something else in the
program tried to loop back to that socket?

The constructor of the object is not guaranteed to run if the object nor anything else in its TU is not accessed from outside. It means the socket might not be opened.
And no, trying to access the object via a network socket does not qualify as "non-initialization odr-use" of the object, as far as the C++ standard is concerned ;-)