"inheritance as reuse" is common but not recommended!I sort of understand why it isn't recommended, but if you'd expound, I'd
appreciate it.
I've been meaning to write a treatise on this for a long time... I will, when I find some free time. See a comment in my blog from July:
http://www.corfield.org/blog/past/2003_07.html#000018
Maybe it wouldn't be so bad if we could extend multiple CFCs?
Argh!!! Noooooooooo!!!! Multiple inheritance BAD! Java learned from C++'s mistake and made sure you could only extend one base class (but you could implement multiple interfaces).
Is it just for the 'convenience' of having a local alias for the data?That, plus I can write my CFC so that it doesn't have to know it got its
data from cache, once it has it. Just one function call and one other minor
change and from then on it's like any other non-cached CFC.
Hmm, OK. And you're comfortable now that you're just keeping a local reference ('instance') to the cached data - you're not actually trying to copy the data into your instance each time?
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).
