On Apr 6, 2005 3:35 PM, Roland Collins <[EMAIL PROTECTED]> wrote: > You wouldn't need super-class checking if you're using the built-in cf > "extends" keyword because you're forcing the contract at compile time > instead of at runtime.
I am using the built-in 'extends' keyword, I'm just exposing a nice way to check for it up an inheritance hierarchy. The 'implements' attribute would be a non-standard extension, but the inheritance stuff is all relying in the builtin metadata. I'm just adding my extra metadata in a way that's consistent with the built-in stuff. -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ---------------------------------------------------------- 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). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
