Isn't "wrong" a bit harsh?
That's why 'wrong' was in quotes - it's subjective.
Don't just tell us it is wrong if it is that big of an issue, give us the skinny details!
I gave some references - go read them :)
If another method is much better, then it ought to be expressed that way.
Design is all about trade-offs. Something that is "much better" in one situation might not be so in another situation.
My point was that Nathan held something up as a "classic example" of inheritance but if you read what the OO gurus have to say about that example, you'll see that they specifically recommend not using inheritance (for the manager/user relationship). Therefore Nathan's example was 'wrong' in the sense that it is not a "classic example" of good inheritance.
Part of the problem with encouraging good OO design is that there are so many examples of poor OO design - even in books (don't get me started on how poor many books are!).
Sean A Corfield -- http://www.corfield.org/blog/
"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 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]
