Agility eLetter February
2005
|
In this issue... In this issue, we have a detailed article on Dealing with Conflicting Interfaces: Part-II. Abstract: In Part I we discussed the issue of conflicting or colliding interfaces and saw how we can address that in Java. While the Java solution is workable, it is not elegant. We can't directly substitute an object of the "implementing" class for the desired interface. .NET offers an interesting facility called "Explicit interface." This allows for a class to override multiple methods with the same signature in a class. Explicit interfaces provide an easy mechanism to implement conflicting interfaces. Please visit http://www.agiledeveloper.com/download.aspx to download the complete article from the Agile Developer web site. |
|
Message from us It has been our
pleasure to be part of the No
Fluff Just Stuff Software Symposium. What I like best about this
symposium is the high quality of speakers and content, and absolutely no
marketing or sales during the event. I am glad to see the event come to Please send suggestions, corrections and comments to agility@agiledeveloper.com. |
|
Quiz corner In .NET, what attribute allows me to exclude calls to methods based on some compile time conditions. Send your response to agility@agiledeveloper.com. This year, each person with the first correct response to the quiz in each issue of Agility will win a special prize. Quiz from the past issue In C#, at runtime, how can I get the name of the executing method? Answer! The correct response is System.Reflection.MethodInfo.GetCurrentMethod().Name (or new System.Diagnostics.StackFrame().GetMethod().Name). Cisco is our winner for January Agility Special Prize. |
|
Subscription Information To subscribe or unsubscribe to the free issues of Agility eLetter, please visit http://www.agiledeveloper.com/eLetter.aspx. |
|
Thus spake... "How should I know if it works? That's
what beta testers are for. I only coded it," Linus Torvalds |