• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            posts - 297,  comments - 15,  trackbacks - 0
            from http://en.wikipedia.org/wiki/Virtual_inheritance

            Virtual inheritance

            From Wikipedia, the free encyclopedia

            Jump to: navigation, search
            For inheritance of virtual functions, see virtual function.

            In the C++ programming language, virtual inheritance is a kind of inheritance that solves some of the problems caused by multiple inheritance (particularly the "diamond problem") by clarifying ambiguity over which ancestor class members to use. It is used when inheritance is representing restrictions of a set rather than composition of parts. A multiply-inherited base class is denoted as virtual with the virtual keyword.

            Contents

            [hide]

            [edit] The problem

            Consider the following class hierarchy.

            class Animal 
            {
            public:
            virtual void eat();
            };

            class Mammal : public Animal
            {
            public:
            virtual Color getHairColor();
            };

            class WingedAnimal : public Animal
            {
            public:
            virtual void flap();
            };

            // A bat is a winged mammal
            class Bat : public Mammal, public WingedAnimal {};

            Bat bat;

            But how does bat eat()? As declared above, a call to bat.eat() is ambiguous. One would have to call either bat.WingedAnimal::Animal::eat() or bat.Mammal::Animal::eat().

            This situation is sometimes referred to as diamond inheritance because the inheritance diagram is in the shape of a diamond. Virtual inheritance can help to solve this problem.

            [edit] Class representation

            Before going further it is helpful to consider how classes are represented in C++. In particular, inheritance is simply a matter of putting parent and child class one after the other in memory. Thus Bat is really (Animal,Mammal,Animal,WingedAnimal,Bat) which makes Animal duplicated, causing the ambiguity.

            [edit] Solution

            We can redeclare our classes as follows:

            class Animal 
            {
            public:
            virtual void eat();
            };

            // Two classes virtually inheriting Animal:
            class Mammal : public virtual Animal
            {
            public:
            virtual Color getHairColor();
            };

            class WingedAnimal : public virtual Animal
            {
            public:
            virtual void flap();
            };

            // A bat is still a winged mammal
            class Bat : public Mammal, public WingedAnimal {};

            Now the Animal portion of Bat::WingedAnimal is the same Animal as the one used by Bat::Mammal, which is to say that a Bat has only one Animal in its representation and so a call to Bat::eat() is unambiguous.

            This is implemented by providing Mammal and WingedAnimal with a vtable pointer since, e.g., the memory offset between the beginning of a Mammal and of its Animal part is unknown until runtime. Thus Bat becomes (vtable*,Mammal,vtable*,WingedAnimal,Bat,Animal). Two vtable pointers per object, so the object size increased by two pointers, but now there is only one Animal and no ambiguity. There are two vtables pointers: one per inheritance hierarchy that virtually inherits Animal: One for Mammal and one for WingedAnimal. All objects of type Bat will have the same vtable *'s, but each Bat object will contain its own unique Animal object. If another class inherits Mammal, such as Squirrel, then the vtable* in the Mammal object in a Squirrel will be different from the vtable* in the Mammal object in a Bat, although they can still be essentially the same in the special case that the squirrel part of the object has the same size as the Bat part, because then the distance from the Mammal to the Animal part is the same. The vtables are not really the same, but all essential information in them (the distance) is.



            posted on 2009-04-29 22:53 chatler 閱讀(242) 評論(0)  編輯 收藏 引用 所屬分類: C++_BASIS
            <2009年11月>
            25262728293031
            1234567
            891011121314
            15161718192021
            22232425262728
            293012345

            常用鏈接

            留言簿(10)

            隨筆分類(307)

            隨筆檔案(297)

            algorithm

            Books_Free_Online

            C++

            database

            Linux

            Linux shell

            linux socket

            misce

            • cloudward
            • 感覺這個博客還是不錯,雖然做的東西和我不大相關,覺得看看還是有好處的

            network

            OSS

            • Google Android
            • Android is a software stack for mobile devices that includes an operating system, middleware and key applications. This early look at the Android SDK provides the tools and APIs necessary to begin developing applications on the Android platform using the Java programming language.
            • os161 file list

            overall

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            久久天天躁狠狠躁夜夜avapp| 久久久久亚洲av成人无码电影| 亚洲欧美精品一区久久中文字幕| 波多野结衣久久一区二区 | 久久精品亚洲精品国产色婷| 久久久久久九九99精品| 成人亚洲欧美久久久久| 久久久久久国产精品无码下载| 久久国产精品-国产精品| 久久人人超碰精品CAOPOREN| 欧美喷潮久久久XXXXx| 久久婷婷五月综合色99啪ak| 国产麻豆精品久久一二三| 中文字幕精品久久| 久久精品无码免费不卡| 国产精品免费福利久久| 99久久国产宗和精品1上映 | 精品伊人久久大线蕉色首页| 久久综合久久综合久久| 国产精品99久久99久久久| 国产精品亚洲综合久久| 看全色黄大色大片免费久久久| 国内精品久久久人妻中文字幕 | 国产99久久久国产精品~~牛| 一本色道久久综合亚洲精品| 久久国产精品无| 中文成人无码精品久久久不卡| 国产精品热久久毛片| 成人精品一区二区久久久| 久久国产乱子精品免费女| AV色综合久久天堂AV色综合在| 国产激情久久久久久熟女老人| 久久久久久午夜精品| 久久99热这里只有精品66| 国内精品久久久久影院亚洲| 亚洲а∨天堂久久精品| 亚洲午夜精品久久久久久app| 久久午夜无码鲁丝片午夜精品| 日韩精品无码久久一区二区三| 久久精品中文字幕一区| 四虎久久影院|