VTT clarification

[Jim Dehnert]

A virtual primary base may move in a further-derived type.  Does that
matter, i.e. would it change the VTT layout when embedded in a VTT for
a more-derived type?

Jim

Mark Mitchell wrote:
> 
> The VTT description is slightly confusing:
> 
>   - The description for `secondary virtual pointers' specifies which
>     subobjects get secondary virtual pointers.  As written, it
>     suggests that even secondary virtual pointers for primary base
>     classes are included.
> 
>   - The note before the example says:
> 
>     secondary virtual pointers are present for all bases with either
>     virtual bases or virtual function declarations overridden along a
>     virtual path. The only exception is that a primary non-virtual
>     base class does not require a secondary virtual pointer.
> 
> If there are not supposed to be secondary virtual pointers for primary
> bases (and I think that there should not be), then that should go in
> the description of secondary virtual pointers; the notes should be
> informational, rather than normative.
> 
> --
> Mark Mitchell                   mark at codesourcery.com
> CodeSourcery, LLC               http://www.codesourcery.com