• <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
            <2009年4月>
            2930311234
            567891011
            12131415161718
            19202122232425
            262728293012
            3456789

            常用鏈接

            留言簿(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无码免费网| 精品久久亚洲中文无码| 日韩人妻无码一区二区三区久久| 99精品久久久久久久婷婷 | 亚洲国产精品婷婷久久| 欧美久久综合九色综合| 色99久久久久高潮综合影院| 亚洲日本久久久午夜精品| 久久久www免费人成精品| 日本久久久久亚洲中字幕 | 深夜久久AAAAA级毛片免费看| 亚洲愉拍99热成人精品热久久| 久久久免费精品re6| 亚洲天堂久久精品| 99久久国产综合精品女同图片| 久久久久四虎国产精品| 久久久国产精华液| 国产精品99久久免费观看| 欧美久久久久久| 亚洲狠狠综合久久| 亚洲中文字幕久久精品无码喷水 | 亚洲综合伊人久久综合| 久久中文字幕视频、最近更新| 亚洲精品国产美女久久久 | 国产精品免费看久久久| 无码人妻精品一区二区三区久久久| 狠狠狠色丁香婷婷综合久久五月| 久久久综合香蕉尹人综合网| 国产三级久久久精品麻豆三级| 久久精品一区二区三区中文字幕| 精品无码久久久久久午夜| 一个色综合久久| 要久久爱在线免费观看| 国产精品xxxx国产喷水亚洲国产精品无码久久一区 | 久久久久亚洲精品天堂久久久久久| 99久久国产综合精品网成人影院| 久久综合久久自在自线精品自| 伊人久久大香线蕉综合热线| 久久久久国产成人精品亚洲午夜|