• <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年1月>
            272829303112
            3456789
            10111213141516
            17181920212223
            24252627282930
            31123456

            常用鏈接

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

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            伊人久久大香线蕉AV一区二区| 看全色黄大色大片免费久久久| 亚洲va中文字幕无码久久不卡| 久久精品中文无码资源站| 久久精品中文闷骚内射| 国产精品女同一区二区久久| 久久久久国产精品人妻| 久久久久久久99精品免费观看| 久久青青色综合| 四虎国产精品免费久久久| 国产99久久久国产精品小说| 久久亚洲欧美日本精品| 久久精品国产亚洲av麻豆蜜芽| 品成人欧美大片久久国产欧美| 国内精品久久久久久久久电影网| 久久精品国产亚洲av麻豆图片| 日韩精品久久久久久| 午夜不卡久久精品无码免费| 久久精品国产亚洲AV不卡| 2020久久精品国产免费| 伊人久久大香线蕉综合影院首页| 国产激情久久久久影院老熟女免费| 色偷偷久久一区二区三区| 久久夜色精品国产噜噜亚洲a| 99久久综合国产精品二区| 99久久777色| 国内精品久久久久影院免费| 久久香蕉国产线看观看精品yw| 久久人做人爽一区二区三区| 亚洲欧美日韩精品久久亚洲区 | 国产精品青草久久久久婷婷| 久久久久亚洲AV成人网人人网站 | 久久99热国产这有精品| 久久狠狠高潮亚洲精品| 国产综合久久久久久鬼色| 亚洲va久久久噜噜噜久久男同| 中文字幕日本人妻久久久免费 | 久久99精品国产| 日韩精品久久久久久| 久久国产成人亚洲精品影院| 久久99精品久久久久久水蜜桃 |