Right now, during the init() of the main CFC I'm loading oracle.cfc
and copying the methods to the base cfc and so forth for any other
imports I'd like to do. Problem is that this is not very elegant.
What's wrong with just instantiating the utility CFCs as data members and accessing the (public) methods directly? Heck, what's wrong with just <cfinclude>ing the file containing the raw UDFs into your CFC (outside any methods), thus making them non-public members of your own CFC?
extend these utlility cfcs in some sort of mind numbing chain of
complexity using... extends. Which, by the way, really sucks and
limits you from actually using extend properly.
Correct. Inheritance is absolutely not the right approach for this.
Team Fusebox -- http://fusebox.org/
Got Gmail? -- I have 50, yes 50, invites to give away!
"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 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]
