> Isn't "wrong" a bit harsh? Will his application crash if he does it that > way? Don't just tell us it is wrong if it is that big of an issue, give us > the skinny details!
The more i study object models, the more it's clear to me that the guiding principle behind "wrong" or "right" is simply a question of how well the model will hold up as the application evolves over time. It's easy to throw something together that runs today, using extension to facilitate today's code reuse for instance, but that's not the point of OO. "Wrong" happens later, when six months down the line you need to change something and suddenly realize, "whoops, that was wrong to do it that way!" and have to rework the core of your app. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
