On Jun 1, 2004, at 12:24 PM, Nathan Dintenfass wrote:
However, from the perspective of "OO" design, extending that CFC everywhere
is actually a practice generally considered a bad idea -- the "best
practice" is to use extends only when you are expressing an "is a"
relationship -- not just to reuse code across components. If you wanted to
be a bit cleaner about it, but still use your single CFC to hold "global
functions", you could instantiate your global CFC inside your other
components, and/or pass your global CFC into your other components as part
of their "init".
In addition to painting yourself into a corner from a design standpoint, you
are also adding non-trivial overhead to all of your CFC instantiations by
extending another heavy CFC -- that will be a particular problem if you
aren't caching most of your CFCs globally when you use them.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words '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]
