Databases
StackOverflow2013
Postsdbo
POInherit interfaces which share a method name
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POInherit interfaces which share a method name
    primarykey
    data
    text
    <p>There are two base classes have same function name. I want to inherit both of them, and over ride each method differently. How can I do that with separate declaration and definition (instead of defining in the class definition)?</p> <pre><code>#include &lt;cstdio&gt; class Interface1{ public: virtual void Name() = 0; }; class Interface2 { public: virtual void Name() = 0; }; class RealClass: public Interface1, public Interface2 { public: virtual void Interface1::Name() { printf("Interface1 OK?\n"); } virtual void Interface2::Name() { printf("Interface2 OK?\n"); } }; int main() { Interface1 *p = new RealClass(); p-&gt;Name(); Interface2 *q = reinterpret_cast&lt;RealClass*&gt;(p); q-&gt;Name(); } </code></pre> <p>I failed to move the definition out in VC8. I found the Microsoft Specific Keyword __interface can do this job successfully, code below:</p> <pre><code>#include &lt;cstdio&gt; __interface Interface1{ virtual void Name() = 0; }; __interface Interface2 { virtual void Name() = 0; }; class RealClass: public Interface1, public Interface2 { public: virtual void Interface1::Name(); virtual void Interface2::Name(); }; void RealClass::Interface1::Name() { printf("Interface1 OK?\n"); } void RealClass::Interface2::Name() { printf("Interface2 OK?\n"); } int main() { Interface1 *p = new RealClass(); p-&gt;Name(); Interface2 *q = reinterpret_cast&lt;RealClass*&gt;(p); q-&gt;Name(); } </code></pre> <p>but is there another way to do this something more general that will work in other compilers?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGohan
    1. USGohan
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POInherit interfaces which share a method name
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POInherit interfaces which share a method name
      1. USrplusg
      1. VTFavorite
    3. VO
      singulars
      1. POInherit interfaces which share a method name
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy do you want this? It seems you're defeating the purpose of virtual functions; you're simply replicating non-virtual semantics. Do you have a reference for `__interface`? I looked it up and it doesn't appear to do anything essential.
      singulars
      1. POInherit interfaces which share a method name
      1. USPotatoswatter
    2. COI added the __interface way.
      singulars
      1. POInherit interfaces which share a method name
      1. USGohan
    3. COPotatoswatter - the reason that you might need to do this is that you might have a class that brings together two different concepts by inheriting from two interfaces. The users of the class likely use it through the interfaces and the users of the two different interfaces don't know or care about each other. The class brings these together and needs to differentiate between calls on one interface and calls on the other. In no way are you defeating the purpose of virtual functions. Gohan - I'd be surprised if __inteface made a difference here.
      singulars
      1. POInherit interfaces which share a method name
      1. USLen Holgate
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload