From: John Love-Jensen <eljay@adobe.com>
To: Sean MacLennan <seanm@seanm.ca>, MSX to GCC <gcc-help@gcc.gnu.org>
Subject: Re: G++ and constructors
Date: Tue, 06 Mar 2007 14:58:00 -0000 [thread overview]
Message-ID: <C212BEC7.1D26F%eljay@adobe.com> (raw)
In-Reply-To: <C212BE33.1D26D%eljay@adobe.com>
Note:
I put in the init_instance() presuming you wanted to do some extra work in
there -- such as whatever lock() and unlock() are doing.
If you don't need to do any extra work, then you can collapse it to the
simpler:
----------------------------------------------------------------------
myclass* myclass::get_instance() // public: static
{
static myclass* instance = new myclass;
return instance;
}
----------------------------------------------------------------------
Sorry if I previous more complicated example caused confusion.
--Eljay
next prev parent reply other threads:[~2007-03-06 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 2:37 Sean MacLennan
2007-03-06 12:46 ` John Love-Jensen
2007-03-06 14:58 ` John Love-Jensen [this message]
2007-03-07 16:40 ` Daniel Lohmann
2007-03-08 17:16 ` Ian Lance Taylor
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=C212BEC7.1D26F%eljay@adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=seanm@seanm.ca \
/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).