From: Gigi Sullivan <sullivan@sikurezza.org>
To: gcc-help@gcc.gnu.org
Subject: __attribute__((constructor)) and order of calls
Date: Thu, 24 Oct 2002 11:58:00 -0000 [thread overview]
Message-ID: <20021024190540.GD892@kappei.pacana.org> (raw)
Aiee :)
Hello!
Let suppose that I've 2 or more functions which are "characterized"
by the __attribute__((constructor)) attribute.
I'm just wondering if there's a clean way to know the routines' order
of call.
Does the same rule, if any, apply to destructor attribute as well ?
TIA, bye
-- gg sullivan
--
Lorenzo Cavallaro `Gigi Sullivan' <sullivan@sikurezza.org>
Until I loved, life had no beauty;
I did not know I lived until I had loved. (Theodor Korner)
next reply other threads:[~2002-10-24 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 11:58 Gigi Sullivan [this message]
2002-10-31 4:11 ` Arunachalam G
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=20021024190540.GD892@kappei.pacana.org \
--to=sullivan@sikurezza.org \
--cc=gcc-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).