You can simplify your code, IMHO by using inheritance between your CFC objects.
Interesting, can you explore your reasoning for this design? I don't see the concept. To me inheritance if to make a more specific object out of a more general object. You have a Prius Object extend a car object, so that it has all the properties and methods of a car plus what makes a Prius unique from other cars. I don't see how a player is a more specific type of table or deck is a more specific type of table. In my "model" I had a table which contains an array of Player objects and a deck object. The Player object(s) contain a Hand object. These Hand objects each contain an array of Card objects. This has worked well so far, until I needed to manipulate this array of Cards, by removing and adding to the array. This is concept I am trying to get a clear picture of. -------------- Ian Skinner Web Programmer BloodSource www.BloodSource.org Sacramento, CA --------- | 1 | | --------- Binary Soduko | | | --------- "C code. C code run. Run code run. Please!" - Cynthia Dunning Confidentiality Notice: This message including any attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and delete any copies of this message. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260555 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
