Sean Corfield showed something along the same lines several months back at
BACFUG. Unfortunately, the main issue is that using this machinery at
run-time would typically be much more overhead than you'd want given the
benefit of the check.
Yes, there's a lot of problems with trying to implement (sic) any sort of interface machinery within CFMX itself. The run-time validation overhead of what I showed at BACFUG and what Eric showed here would typically be unacceptable in a production app.
Then there's the whole issue of why you really want interfaces in the first place: you want to be able to declare functions that take arguments of that interface type and/or return instances of (implementations of) that interface type. CF simply doesn't let you make that happen in any reasonable way.
Until CF natively supports interfaces, you just cannot workaround the issue.
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]
