Nested Classes or Alternative?

[Rudolf Ball]

Hi NG,

I want to build two classes,

Demo.Car (where Demo is the Namespace) and
Demo.Car.Wheel

Is the only solution a nested Class? Isn`t there anything more elegant?

Thank you

Rudi

 

[=?ISO-8859-2?Q?Marcin_Grz=EAbski?=]

Hi Rudi,

I want to build two classes,

Demo.Car (where Demo is the Namespace) and
Demo.Car.Wheel

Is the only solution a nested Class? Isn`t there anything more elegant?

What do you say about:
Demo.CarParts.Wheel (where "Demo.CarParts" is the namespace) ?

Usually the nested classes are those classes which instances
lives only in their "main class" object, and are initialized
usually by "main class".

In your case word "elegant" should replaced with "functional".

Regards

Marcin

 

[Tamir Khason]

You can use reference wich points to our class, but why you need it? Why not
to make Wheel Property of Car of Wheel type???
namespace Demo
{
class Car
{
Wheel m_wheel;
public Wheel Wheel
{
get {return m_wheel;}
set {m_wheel = value;}
}
}
}

Now you can use
Demo.Car.Wheel = new Weel(whatever);
Demo.Car.Wheel.Tyre = new Tyre(TyreTypes.Michelin); //