Deutsch   English   Français   Italiano  
<vsc0jp$2294v$1@raubtier-asyl.eternal-september.org>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!raubtier-asyl.eternal-september.org!.POSTED!not-for-mail
From: Bonita Montero <Bonita.Montero@gmail.com>
Newsgroups: comp.lang.c++
Subject: Re: Pre-main construction order in modules
Date: Sun, 30 Mar 2025 19:56:27 +0200
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <vsc0jp$2294v$1@raubtier-asyl.eternal-september.org>
References: <vsb12i$2mv42$1@dont-email.me>
 <aac70dc2990a43c684e920a10f9e2024a3defcd8@i2pn2.org>
 <sdeGP.730205$J61.626544@fx08.ams4>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 30 Mar 2025 19:56:09 +0200 (CEST)
Injection-Info: raubtier-asyl.eternal-september.org; posting-host="2cd8a133533088b08c4cfe8295267243";
	logging-data="2172063"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/OnTkQd+5JqqynO2WrCPQjmoTx2J2wjO4="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:IKjCelHr6mmdGaRoepcYhPxHjuc=
In-Reply-To: <sdeGP.730205$J61.626544@fx08.ams4>
Content-Language: de-DE
Bytes: 2033

Am 30.03.2025 um 18:22 schrieb Mr Flibble:
> On Sun, 30 Mar 2025 07:21:14 -0400, Richard Damon wrote:
> 
>> On 3/30/25 4:57 AM, Muttley@DastardlyHQ.org wrote:
>>> I was curious about the order in which objects get constructed in
>>> modules before main gets called. It seems with both Clang and gcc its
>>> the order in which the modules were linked together to form the
>>> runnable binary so if the link order was m1.o m2.o then anything in m1
>>> would get constructed first.
>>> Vice verca if you switch the order.
>>>
>>> Is this codified in the standard or is it left up to compiler and
>>> linker writers to decide how they order this?
>>>
>>>
>> It is left explicitly undefined in the Standard.
> 
> No, it is *unspecified* not *undefined*.

LOL - idiot