further about Inheritance

Code:

---

class Vehicle
{

private:
int modelno;
char name;
string regno;

public:

int getmodel();
int setmodel();
void addregno():

};

class Car: public Vehicle
{

};

---

hi guys

I wanted to know that is their a way to restrict the derived class "Car" so that it could only use addregno() function of the base class "Vehicle"?

by addregno I mean registeration number.


Does "string" data type allows us to have a characters with both numeric and alphabets?


Thanks

Quote:

---

Originally Posted by student111

I wanted to know that is their a way to restrict the derived class "Car" so that it could only use addregno() function of the base class "Vehicle"?

by addregno I mean registeration number.


Does "string" data type allows us to have a characters with both numeric and alphabets?


Thanks

---

1.Just make the other functions private.
2.Yes

Hi

Thanks for the reply, ok but if I just want to restrict the derived class "Car" to only use that function, so can I just mention that function in the public portion of the derived class "Car"? Will that be the same thing?

Also if I don't write the public before the base class "Vehicle" as:

Code:

---

class Car : Vehicle

{



};

---

Will this code be wrong?

Quote:

---

Originally Posted by student111

Thanks for the reply, ok but if I just want to restrict the derived class "Car" to only use that function, so can I just mention that function in the public portion of the derived class "Car"? Will that be the same thing?

---

Let's talk a little about interfaces: suppose you're writing the main function. What member functions of the Vehicle class would you expect to use? What about the Car class?

Quote:

---

Originally Posted by student111

Will this code be wrong?

---

No, but it means that you would be using private inheritance.

Btw, if your Car is inheriting from a Vehicle, it is a good idea to make the car able to do everything a vehicle should be able to do.

It may do it a little differently, but it removing functionality down the ladder of inheritance isn't a good idea or design, in my opinion.

Here you go again...posting on an old thread intentionally trying to prove me wrong.
I suggest that you think carefully about what I wrote, before trying to counter it.

The base class is the most general type...often used as an interface.
If the classes derived from it do not support the same interface, it will be a violation of the Liskov substitution principle; and will be a broken design.

Quote:

---

I think you should read a good book on programming and understand the concept of "specialization" in C programming.

---

I think you should be careful. This comment could swing either way but because you've already been warned about your behavior today we are much all going to interpret this as a comment with intent to directly insult.

Quote:

---

You will learn how to restrict a perticular behaviour for a perticular derived class .

---

O_o

This isn't C where "classes" are hidden solely behind abstract interfaces.

This is C++ where classes are "first class" where "public inheritance" means I can get those pesky restrictions of the derived class to evaporate by using a base class pointer.

Besides, a derived class must not add restrictions to an interface less it break substitution; a derived class must only lessen restrictions.

Soma