From: Daniel Jacobowitz <drow@false.org>
To: Ross Boylan <ross@biostat.ucsf.edu>
Cc: gdb@sourceware.org
Subject: Re: Associating C++ new with constructor
Date: Thu, 15 Feb 2007 13:35:00 -0000 [thread overview]
Message-ID: <20070215115014.GA26850@caradoc.them.org> (raw)
In-Reply-To: <20070215073516.GW5871@wheat.betterworld.us>
On Wed, Feb 14, 2007 at 11:35:16PM -0800, Ross Boylan wrote:
> Does that have any chance of working with any generality?
No, none. The compiler can do an arbitrary amount of work between the
two calls. They can end up with branches in between, or a call to new
could be used to conditionally create one of two objects that happen
to have the same size.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-15 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 11:50 Ross Boylan
2007-02-15 13:35 ` Daniel Jacobowitz [this message]
2007-02-15 15:38 ` Michael Veksler
2007-02-15 21:24 ` Ross Boylan
2007-02-15 22:10 ` Michael Veksler
2007-02-16 5:03 ` Ross Boylan
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=20070215115014.GA26850@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=ross@biostat.ucsf.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