If you use the second method then you HAVE to explicitly cast to the correct interface everytime. tt.DoStuff() alone will not work.
Main Topics
Browse All Topics
Loading Advertisement...
Question
multiple inheritance/implementation
If I inherit 2 or more interfaces that have the same method name/signiture what happens.
Do I get to implement it one, twice or will it not build; or something else.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Subscribe now for full access to Experts Exchange and get
Instant Access to this Solution
- Plus...
- 30 Day FREE access, no risk, no obligation
- Collaborate with the world's top tech experts
- Unlimited access to our exclusive solution database
- Never be left without tech help again
Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.
- "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
- "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
- "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.
See what Experts Exchange can do for you.
Got a question?
We've got the answer.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
Need individual assistance?
Our experts are ready to help.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Want to learn from the best?
Read articles from industry experts.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Working on a long term project?
Store your work and research.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
What Makes Experts Exchange Unique?
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Trusted by the world's most respected brands.
Faithfully serving IT professionals since 1996.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Free Tech Articles
-
WARNING: 5 Reasons why you should NEVER fix a computer for free.
It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
-
SCCM OSD Basic troubleshooting
SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
-
Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
-
Create a Win7 Gadget
This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
-
Outlook continually prompting for username and password
There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
-
Backup Exchange 2010 Information Store using Windows Backup
There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...
Cloud Class Webinars
- Avoiding Bugs in Microsoft Access
Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
- Top 10 Best New Features in Visio 2010
Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
- IT Consultant Business Secrets Revealed
Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
- Disaster Recovery and Business Continuity
Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
- Organize Your Visio Diagrams with Containers and Lists
Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
- How to Us Objects, Properties, Events and Methods in Microsoft Access
Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...
Join the Community
Give a Little. Get a Lot.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Answers
You need to implement both methods providing full qualified name:
interface IDimensions
{
float getLength();
float getWidth();
}
interface ISize
{
float getLength();
float getWidth();
}
class Box : IDimensions, ISize
{
float IDimensions.getLength()
{
...
}
float IDimensions.getWidth()
{
...
}
float ISize.getLength()
{
...
}
float ISize.getWidth()
{
...
}
}
From the client code, you can call these functions using interface reference.
<correction to previus post, sorry about that>
That explains most of it.
I assume using the first example, I could rewrite main as:
static void Main(string[] args)
{
ThisThat tt = new ThisThat();
IDoThis DoThis = tt;
IDoThat DoThat =tt
DoThis.DoStuff();
DoThat.DoStuff();
}
The extra bit im not so shour about is this example:
interface IDo
{
void DoStuff();
}
interface IDoThis : IDo
{
}
interface IDoThat : IDo
{
}
class ThisThat : IDoThis, IDoThat
{
void IDoThis.DoStuff()
{
Console.WriteLine("IDoThis
}
void IDoThat.DoStuff()
{
Console.WriteLine("IDoThat
}
}
static void Main(string[] args)
{
ThisThat tt = new ThisThat();
IDo Do = tt;
Do.DoStuff(); //which one is called
((IDo)tt).DoStuff(); //which one is called
}
Thanks in advance
Richard.
That code shouldn't compile.
DoStuff doesn't explicitly belong to the IDoThis and IDoThat interfaces, it belongs to the IDo interface. So in order to explicitly implement it you would have to use IDo.DoStuff().
Because DoStuff is the base for both IDoThis and IDoThat then what you end up with is an merger or the unique signatures, so there is only one DoStuff() method rather than on for each of the two derived interfaces. Therefore, no explicit declaration is needed, you simply use: void DoStuff(), to implement the method as defined in the base interface.
In practical terms you shouldn't realisticly inherit a class from two interfaces with the same base.
Hope that made sense.
3 Ways to Join
Business Accounts
- Perfect for organizations
- Multiple users
- Save over 36%
- Create a Business Account
Answer for Membership
- Earn free access
- Showcase your knowledge
- No credit card required
- Sign Up to Answer
Loading Advertisement...
by: carl_tawnPosted on 2006-03-31 at 08:48:26ID: 16344085
You can implement one method that satisfies the signature for both interfaces.
class ThisThat : IDoThis, IDoThat
{
public void DoStuff()
{
Console.WriteLine("Doing stuff");
}
}
interface IDoThis
{
void DoStuff();
}
interface IDoThat
{
void DoStuff();
}
static void Main()
{
ThisThat tt = new ThisThat();
tt.DoStuff();
}
Or, you can specify one for each, in which case you have to cast to the interface you want to use:
class ThisThat : IDoThis, IDoThat
{
void IDoThis.DoStuff()
{
Console.WriteLine("IDoThis
}
void IDoThat.DoStuff()
{
Console.WriteLine("IDoThat
}
}
interface IDoThis
{
void DoStuff();
}
interface IDoThat
{
void DoStuff();
}
static void Main(string[] args)
{
ThisThat tt = new ThisThat();
((IDoThis)tt).DoStuff();
((IDoThat)tt).DoStuff();
Console.ReadLine();
}
Hope this helps.