Re: Confusion With Inheritance

Hi there Robert, H.S. Lahman, and Micahel, thank you all for your
comments and suggestions.

Robert, you are of course correct in your assumption that the Product
class has behaviour other than displaying itself.

> Displaying the product must be relegated to some
> outlying classes.

Perhaps something like ProductViewer? ProductViewer could consist of
one static/shared function called GetProductData that accepts a Product
as a parameter and returns the appropriate information.

> Object Oriented Design is a discipline for
> partitioning *behavior*, and *incidentally* the data that goes with
> that behavior.

Let's say the Product class does survive as a class. Am I correct in
assuming that you would discourage subclassing SkinCare products and
Makeup products and instead design a single Product class that had
UNDEFINED attributes depending on the type of product that was
instantiated?

Just to summarise, I think there are two issues that are being
discussed now. The first is the actual design of the Product class (or
classes, depending on your approach), and the second is the best way to
display a Product to the user.

.