|
This is why I only rarely ask questions of
this list… you’re too smart for my own good. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Stoner On 10/13/05, David
Ross <[EMAIL PROTECTED]>
wrote: The type checking is the most important feature, as it enables you
to... While your second solution is a resonable idea, why would you not marry
it with compile time vaildation and your extended (improved) "method not
implemented" error messages? I agree that runtime interface
validation/method checking would be a hog but there is no reason that
the object cannot earn the right to "claim to implement" at
compile time. I dislike people who are intolerant of other people's cultures and the
Dutch ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] |
- RE: [CFCDev] inheritance advice Paul
- RE: [CFCDev] inheritance advice Ung, Seng
- Re: [CFCDev] inheritance advice Chris Stoner
- Re: [CFCDev] inheritance advice Chris Stoner
- Re: [CFCDev] inheritance advice Sean Corfield
- Re: [CFCDev] inheritance advice Muzak
- RE: [CFCDev] inheritance advice John Ottenbacher
- Re: [CFCDev] inheritance advice Muzak
- RE: [CFCDev] inheritance advice Stijn Dreezen
