Re: Inheritance/Polymorphism - C# Discussion Boards

4-Feb-10 18:26

Hello all, my name is Sundeepan and I am new to this board and to coding as well. To train myself and get familiar with OOP concepts using the C# language I am reading, "Microsoft .NET Framework - Application Development Foundation" book by Tony Northrup. I am finding this book very informative. I do have a question that I was not able to find an answer to by querying Google. The question is as follows:

If a method requires an object as one of its parameters why should one not pass an object of a base class, instead one must pass an object of the derived class?

I understand that this might be a foolish question, but I am at a very early stage of my learning, any help would be appreciated. Metaphors are equally as helpful as a technical answer.

Regards

Sundeepan

http://sundeepinthought.blogspot.com

modified on Friday, February 5, 2010 12:32 AM

Not Active4-Feb-10 20:07

Not Active

4-Feb-10 20:07

class Animal
{
   protected void Foo(){}
}

class Cow : Animal
{
   public vod Moo(){}
}

class Farm
{
   public void Pet(Animal animal){}
}

If you pass Animal to a method then you can only access the Foo method. However, if you pass Cow, you will have access to both Moo and Foo methods since Cow derives from Animal.

I know the language. I've read a book. - _Madmatt

Sundeepan Sen4-Feb-10 20:28

4-Feb-10 20:28

So if I wrote

class Farm
{
    public void Pet(Cow chicken){}
}

I can access both Foo and Moo?

But if I wrote

 class Farm
{
    public void Pet(Animal man){}
}

then I can only access the Foo method?

Lol..nice example though....clarification is needed if you don't mind Big Grin | :-D

Wamuti4-Feb-10 21:58

Wamuti

4-Feb-10 21:58

sundeepan wrote:
Cow chicken

and

sundeepan wrote:
Animal man

was a really comical. Laugh | :laugh:

Anyway i don't see any clarification to make since it is just as you say. When you inherit, you get the members you inherit and in addition any member you make in the new class. Just like if someone left you some items to travel to an unknown land ( Dead | X|

) then, you'd have the items you originally owned plus the ones he left you. But he would not have the items you own since you never gave it to them.

Wamuti: Any man can be an island, but islands to need water around them!
Edmund Burke: No one could make a greater mistake than he who did nothing because he could do only a little.

PIEBALDconsult5-Feb-10 3:19

PIEBALDconsult

5-Feb-10 3:19

sundeepan wrote:
why should one not pass an object of a base class

Who says you shouldn't? There are many cases where you would.

Sundeepan Sen5-Feb-10 7:04

5-Feb-10 7:04

This is the paragraph that threw me off:

"Another benefit of inheritance is the ability to use derived classes interchangeably, a concept called polymorphism. For example, there are five classes that inherit from the System.Drawing.Brush base class: HatchBrush, LinearGradientBrush, PathGradientBrush, SolidBrush, and TextureBrush. The Graphics.DrawRectangle method requires a Brush object as one of its parameters however, you never pass an object of the base Brush class to Graphics.DrawRectangle. Instead you pass an object of one of the derived classes. Because they are each derived from the Brush class, the graphics.DrawRectangle method can accept any of them. Similarly if you were to create a custom class derived from the Brush class, you could also pass an object of that class to Graphics.DrawRectangle. "

PIEBALDconsult5-Feb-10 7:50

PIEBALDconsult

5-Feb-10 7:50

It sounds like the author isn't a very good technical writer. Which is one of my complaints about mass-market programming books. And one of the benefits of taking a class with a real live teacher -- you can ask the teacher for clarification.

That may not be a good example -- System.Drawing.Brush is abstract, so you can't have an instance of it anyway. But if you do have an instance of it, then you could go right ahead and pass it (but who knows what would happen).

Sundeepan Sen5-Feb-10 9:24

5-Feb-10 9:24

Its a "Microsoft Press" book for the 70-536 cert exam...this guy better be a good technical writer lol!

Keith Barrow5-Feb-10 5:23

Keith Barrow

5-Feb-10 5:23

I actually almost say the contrary is true.

Mark Nischalke's answer holds true, you do have access to both the Moo() and Foo() methods by passing the subclass. However to do so couples the method to the subclass, and other instances of the animal class cannot be passed:

class Program
{
    static void MakeAnimalSpeak(Animal animal)
    {
        
        animal.MakeNoise();
    }

    static void MakeAnimalSpeakCoupled(Cow animal)
    {
        // This is more tighltly coupled to cow: 
        // this method cannot be called for duck
        animal.MakeNoise();
    }


    static void Milk(Cow animal)
    {
        animal.Milk();
        animal.MakeNoise(); // Cow is mooing with happiness
    }



    static void Main(string[] args)
    {
        Cow cow = new Cow();
        Duck duck = new Duck();
        MakeAnimalSpeak(cow);
        MakeAnimalSpeak(duck);
        MakeAnimalSpeakCoupled(cow);
        //MakeAnimalSpeakCoupled(duck); //Coupled to cow: this is a worse implementation in this context
        Milk(cow);
        //Milk(duck); //Can't, but not a problem. Milking a duck is nonsensical!
    }
}



abstract class Animal
{   
    public abstract void MakeNoise();  
}

class Cow : Animal
{
    public override void MakeNoise() { Console.WriteLine("Moo"); }
    public void Milk() { Console.Write("Sloooosh"); }
}

class Duck : Animal
{
    public override void MakeNoise() { Console.WriteLine("Quack"); }    
}

Of course it is horses for courses, as with everythign in the code world. In the example Mark gave, you should pass the cow if you need access to both Moo() and Foo() but otherwise IMO is is better to pass an Animal instead. Better yet, coding to Intefraces produces cleaner results still, and helps with testing (as mock objects can be passed more easily)

Cpianism: I have a negative number in my Rep so please fix it.
Chris Maunder: That isn't a bug.

Sundeepan Sen5-Feb-10 10:05

WindowsAPICodePack GlassForm Question

5-Feb-10 10:05

This is great, I like the humor involved too. I am saving this reply as a PDF on my computer.

Thanks again!

harsimranb4-Feb-10 17:06

harsimranb

4-Feb-10 17:06

Hi,

I had a question regarding the Windows Aero Glass Feature, found in Windows API Code Pack. This feature is not included in Windows XP and Vista, I believe. So if the GlassForm is shown in Windows XP, will an error be thrown? or will the GlassForm window be shown, without the aero feature and without anyerror error?

To be more clear: What will happen if the GlassForm is show in Windows XP/Windows Vista?

Thanks,
Harsimran Singh

#realJSOP5-Feb-10 0:17

#realJSOP

5-Feb-10 0:17

WPF also allows aero to be forced on an app, but when you do that, the appropriate DLL is already in the GAC on the user's machine (because they're running the appropriate version of .Net. I suspect that if you include a CodePack assembly in your references, the appropriate DLL will get copied to your bin folder.

Try it and see...

.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

harsimranb5-Feb-10 9:14

harsimranb

5-Feb-10 9:14

Even if I try that, I can't test it. I don't own a XP or a Vista machine. I only have Windows 7.
For more information, you should check out my article: Windows 7 FTP Application

It only runs on Windows 7, because of the Windows 7-specific features. I can control other windows 7-specific features on Windows XP/Vista using if(CoreHelpers.RunningOnWin7), however, some of my forms use the glass form. which I can't really control using CoreHelpers.RunningOnWin7, because a Form inherits from GlassForm to use the GlassForm feature.

First question would be: What happens if GlassForm is shown in Windows XP? Will an error be thrown? It doesn't matter if the aero feature is not shown, since it is Windows XP/Vista. I only require the glass feature in Windows 7.

I hope I am clear,
Thanks,
Harsimran Singh

#realJSOP5-Feb-10 9:37

#realJSOP

5-Feb-10 9:37

Pathachiever wrote:
It only runs on Windows 7, because of the Windows 7-specific features.

If it only runs on Windows 7, then why are you asking about XP? If you don't want it to to run on XP, then do a Windows version check before you display the first form, and terminate the program if it's running on XP.

harsimranb5-Feb-10 14:45

harsimranb

5-Feb-10 14:45

Sorry. I knew I wasn't clear on my side.

Actually, I want the application to run on Windows XP. However, I don't know what will happen if the application is ran on Windows XP, since Windows XP probably does not support the glass form feature.

I hope I am more clear now. I just need to know what will happen when the Glass Form is shown in Windows XP.

Thanks,
Harsimran Singh