Brian K.
You sound just like the Head First OOAD book. The one thing that is always guaranteed in software development is CHANGE. J ===== The key there is to make sure that you keep things as encapsulated as possible so that if, later, you decide you DO need a full blow MembershipType object, it is easy to make that change. That is probably the best advice to highlight: however you choose to do it, take extreme measures to make it easy to refactor later. That means making changes in only one place, and make sure that the impact of a change is isolated and doesn't ripple through the entire system. You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
