>>I'm a big believer that if your a good coder in a different language you'll be a good coder in any language - because it's about the logic and the rest is just syntax. So I was looking for an OOP question that didn't rely on FoxPro knowledge and came up with. Can you describe a deck of cards as objects? Telling me what classes you would create and what properties and methods you would put in each class. To this date only 1 person has ever given me a good response on this question. Is it too tuff of a question or is it a bad question?
>
>A deck of cards is a container. Each card is a "child" of that container. Each card has a property for suite value (clubs - diamonds - etc) and a property face value (1.2...10.J.Q.K.A).
>
>So a deck of cards is an object with 56 children with each child (card) having unique suite and face properties.
Nope. It's a collection of 52 items... unless you want to throw in a few joke(r)s.
Or you can subclass it to have 20, 32, 36, 104, 108 or 110 items. Yes, I used to play some games which required such decks. Well, except the 36 - but I once had such a deck.