From: "Randy Brukardt" <randy@rrsoftware.com>
Subject: Re: Differences in finalization of controlled objects between gcc 4.6 and gcc 4.7
Date: Thu, 19 Jul 2012 21:56:14 -0500
Date: 2012-07-19T21:56:14-05:00 [thread overview]
Message-ID: <juahcg$gg9$1@munin.nbi.dk> (raw)
In-Reply-To: ju93rg$43j$1@speranza.aioe.org
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
"Markus Sch�pflin" <no.spam@spam.spam> wrote in message
news:ju93rg$43j$1@speranza.aioe.org...
> Am 19.07.2012 15:45, schrieb Georg Bauhaus:
>> On 19.07.12 14:23, Markus Sch�pflin wrote:
>>> Is there a way to have the objects created in place directly in the
>>> array?
>>
>> Can you make the type limited?
>
> No, I need to be able to copy them around. But IMHO that shouldn't make a
> difference in this case, the compiler should be able to figure out that it
> can construct the objects in place, shouldn't it?
If the type isn't limited, there are cases where you can't build the objects
in place. And it's likely that the implementation of build-in-place
functions is different than ones that copy (BiP probably passes in some
memory and/or a storage pool; regular just returns a temporary created
inside the function).
It's unlikely that an implementer would want to have two versions of a
function, so its quite possible that they don't ever build-in-place
non-limited objects.
(But there is a permission to do so, so you cannot depend on the Adjust
being called.)
Randy.
next prev parent reply other threads:[~2012-07-26 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 12:23 Differences in finalization of controlled objects between gcc 4.6 and gcc 4.7 Markus Schöpflin
2012-07-19 13:45 ` Georg Bauhaus
2012-07-19 13:59 ` Markus Schöpflin
2012-07-19 14:48 ` Georg Bauhaus
2012-07-20 2:56 ` Randy Brukardt [this message]
2012-07-20 2:59 ` Randy Brukardt
2012-07-27 7:02 ` Markus Schöpflin
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox