public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "John bebbington" <John.Bebbington@t-online.de>
To: help-gcc@gnu.org
Subject: Re: How do I control the order of constuctors
Date: Sat, 01 Jan 2000 03:24:00 -0000	[thread overview]
Message-ID: <84knuq$h5d$1@news04.btx.dtag.de> (raw)
In-Reply-To: <84k4ds02vdb@enews3.newsguy.com>

Johnny Favorite (it means "Writhing Tentacle of Death") wrote in message
<84k4ds02vdb@enews3.newsguy.com>...
>Greg Chicares wrote:
>> It's in the FAQ at
>> http://www.cerfnet.com/~mpcline/c++-faq-lite/
>
>Well, I dug around there for 30 minutes or so and I can't find anything
>about the ordering of constructors before main().  I'd always assumed it
was
>impossible to do anything about the ordering, that it was up to the
>compiler.  If the FAQ says something different I'd like to know what it is.
>
>

Thanks for the link Greg,

I have found what I need is the following sections of the FAQs at
http://www.cerfnet.com/~mpcline/c++-faq-lite/

[10.10] What's the "static initialization order fiasco"?
[10.11] How do I prevent the "static initialization order fiasco"?
[10.12] How do I prevent the "static initialization order fiasco" for my
static data members?



WARNING: multiple messages have this Message-ID

From: "John bebbington" <John.Bebbington@t-online.de>
To: help-gcc@gnu.org
Subject: Re: How do I control the order of constuctors
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <84knuq$h5d$1@news04.btx.dtag.de> (raw)
Message-ID: <20000401000000.BIUQg053Di0H-PM3sTLITRpwdi3l1ModnF3CFMy4T6Q@z> (raw)
In-Reply-To: <84k4ds02vdb@enews3.newsguy.com>

Johnny Favorite (it means "Writhing Tentacle of Death") wrote in message
<84k4ds02vdb@enews3.newsguy.com>...
>Greg Chicares wrote:
>> It's in the FAQ at
>> http://www.cerfnet.com/~mpcline/c++-faq-lite/
>
>Well, I dug around there for 30 minutes or so and I can't find anything
>about the ordering of constructors before main().  I'd always assumed it
was
>impossible to do anything about the ordering, that it was up to the
>compiler.  If the FAQ says something different I'd like to know what it is.
>
>

Thanks for the link Greg,

I have found what I need is the following sections of the FAQs at
http://www.cerfnet.com/~mpcline/c++-faq-lite/

[10.10] What's the "static initialization order fiasco"?
[10.11] How do I prevent the "static initialization order fiasco"?
[10.12] How do I prevent the "static initialization order fiasco" for my
static data members?



  reply	other threads:[~2000-01-01  3:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-31  6:21 John bebbington
1999-12-31  8:39 ` Greg Chicares
1999-12-31 22:24   ` Greg Chicares
1999-12-31 22:24   ` Johnny Favorite (it means "Writhing Tentacle of Death")
2000-01-01  3:24     ` John bebbington [this message]
2000-04-01  0:00       ` John bebbington
1999-12-31 22:24 ` John bebbington

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='84knuq$h5d$1@news04.btx.dtag.de' \
    --to=john.bebbington@t-online.de \
    --cc=help-gcc@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).