From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] I like this one
Date: Tue, 29 Jan 2008 14:29:29 -0800 [thread overview]
Message-ID: <1201645769.28153.100.camel@work.sfbay.sun.com> (raw)
In-Reply-To: <5B08A2ED-67FB-4B6E-8078-277CE0F1AE23@mac.com>
On Tue, 2008-01-29 at 17:11 -0500, Pietro Gagliardi wrote:
> I don't get it... But why would you control how constructors are run?
You don't unless you're totally worried about your job security and
would want to make maintenance of your code code virtually
impossible. ;-) C++ at least was smart enough not to promise anything
about the sequencing of constructors for global objects.
Now, I can bet money that the reason they did it is for shared
libraries. And that opens up a whole new can of worms right there.
Thanks,
Roman.
next prev parent reply other threads:[~2008-01-29 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 21:50 ron minnich
2008-01-29 21:57 ` andrey mirtchovski
2008-01-29 22:11 ` Pietro Gagliardi
2008-01-29 22:29 ` Roman Shaposhnik [this message]
2008-01-29 22:58 ` Bakul Shah
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=1201645769.28153.100.camel@work.sfbay.sun.com \
--to=rvs@sun.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).