On Tue, 23 Nov 2004 09:27:52 -0500, Patrick McElhaney <[EMAIL PROTECTED]> wrote: > One CFC should extend another (or they should both extend a common > base CFC) if they implement the same methods and have the same > pre-conditions, post-conditions, and invariants.
In other words, substitutability. "is-a". > As you pointed out, the "is-a" relationship instead focuses on the > name of the CFC, which is arbitrary, irrelevant to the compiler, and > at best only provides a hint of what the CFC actually does. No, it has nothing to do with the name. > Also, I think the very notion that we need to decide between "is-a" > and "has-a" suggests that we figure out what the CFCs are first and > then figure out how they relate to each other. I haven't managed to > get very far working that way. Yes, in other words, OO modeling is extremely important. > Instead I start my design off with one or two simple CFCs. As I look > at the requirements and add features new CFCs emerge from refactoring. That's a reasonable way to work - OO deisgn is, almost by definition, a very iterative process. -- Sean A Corfield -- http://www.corfield.org/ Team Fusebox -- http://www.fusebox.org/ Breeze Me! -- http://www.corfield.org/breezeme Got Gmail? -- I have 1 invite "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words '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 [EMAIL PROTECTED]
