when put a class in another class

[Wilfried Mestdagh]

Hi,

When do you put a class in another class and when not ? It seems in most
case both work fine, but in some case not. I'm not yet smart enough in dotnet
to know when and wy. Can someone enlighten ?

I give example to enlight what I mean. This one has the CFG class in the
class Rx:
namespace TTLocator
{
public partial class Rx: Form
{
public class CFG
{
}
}
}

This one has the CFG class in the same namespace but outside the Rx class:
namespace TTLocator
{
public partial class Rx: Form
{
}

public class CFG
{
}
}

--
rgds, Wilfried
http://www.mestdagh.biz

[Salvador]

Hi,

Is a design decision, it depends what do you want to achieve, you have to
ask yourself the question:

"Does CFG belong to Rx?

Example 1:

public class Employee : Person
{
public class EmployeeType
}

This example also gives you the oportunity to protect classes, let's suppose
that "EmployeeType" is also for "Employee" use, you just change the modifier
to "private"

Example 2:

public class Employee : Person
{
}

publc class Department
{
}

In this case department is not related at all with the Employee structure.

Hope this helps
Salvador

"Wilfried Mestdagh" wrote:

Hi,

When do you put a class in another class and when not ? It seems in most
case both work fine, but in some case not. I'm not yet smart enough in dotnet
to know when and wy. Can someone enlighten ?

I give example to enlight what I mean. This one has the CFG class in the
class Rx:
namespace TTLocator
{
public partial class Rx: Form
{
public class CFG
{
}
}
}

This one has the CFG class in the same namespace but outside the Rx class:
namespace TTLocator
{
public partial class Rx: Form
{
}

public class CFG
{
}
}

--
rgds, Wilfried
http://www.mestdagh.biz

[JAL]

In general prefer containment over inheritance. Then realize there are
two types of containment, by reference and by ownership.

http://www.geocities.com/jeff_louie/OOP/oop7.htm
http://www.geocities.com/jeff_louie/OOP/oop12.htm

Regards,
Jeff

[Bob Weiner]

When one object is fully dependent of another you would use the ownership
(ie. nested class). If the subordinate object can be used outside the
context of the parent then you would use it by reference.

For instance, a "Wheel" class may have a nested "Spoke" class because the
spoke is useless without the wheel. The "Wallet" class would refer to a
"Money" class because there are LOTS of uses for money!

Inheritance is a different beast altogether which should be used to express
IS-A vice HAS-A relationships. For instance, the "Euro" and "Dollar"
classes would inherit from "Money" and subsequently be refered to by the
"Wallet" class.
bob

"JAL" <Je********@yahoo.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

In general prefer containment over inheritance. Then realize there are
two types of containment, by reference and by ownership.

http://www.geocities.com/jeff_louie/OOP/oop7.htm
http://www.geocities.com/jeff_louie/OOP/oop12.htm

Regards,
Jeff