• <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 閱讀(243) 評論(0)  編輯 收藏 引用 所屬分類: C++_BASIS
            <2010年3月>
            28123456
            78910111213
            14151617181920
            21222324252627
            28293031123
            45678910

            常用鏈接

            留言簿(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

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            亚洲国产婷婷香蕉久久久久久| 色综合久久夜色精品国产| 久久精品亚洲男人的天堂| 久久精品成人欧美大片| 人妻无码久久精品| www性久久久com| 国产精品99久久久久久宅男| 热综合一本伊人久久精品 | 久久人人爽人人精品视频| 无码人妻久久一区二区三区免费 | 亚洲国产精品狼友中文久久久| 伊人久久综合无码成人网 | 久久亚洲精品无码AV红樱桃| 91久久精品视频| 国产精品99久久精品| 久久热这里只有精品在线观看| 国产免费久久精品99久久| 伊人久久大香线蕉亚洲| 久久影院午夜理论片无码| 国内精品久久久久久野外| 久久久久亚洲AV无码网站| 久久久噜噜噜www成人网| 亚洲国产精品嫩草影院久久| 99久久99久久精品国产片果冻| 久久久久亚洲AV无码麻豆| 久久综合视频网| 久久精品亚洲欧美日韩久久| 99久久99久久| 国产精品美女久久久久| 浪潮AV色综合久久天堂| 国内精品久久久久影院亚洲| 久久人人爽人人人人片av| 久久免费99精品国产自在现线| 国产成人香蕉久久久久| 国产精品久久久久久搜索| 国产成年无码久久久久毛片| 久久精品中文騷妇女内射| 人妻无码αv中文字幕久久| 久久久国产乱子伦精品作者| 青草国产精品久久久久久| 欧美噜噜久久久XXX|