I'm under the impression that you can persist functions, just like any other variable.
I'm not sure why you'd want to do that, though, if there isn't data "Stored" Between function calls. ( and if there is data stored between function calls use a CFC).
At 11:37 AM 6/1/2004, you wrote:
This is how I view it. I try to maintain a seperation between CFFUNCTION and CFCOMPONENT.
Generally, if I want to cache/persist the function, or play with properties and the such, I'll use a CFC. If however, it just a refactoring (such as anything found on cflib.org), I'll leave it just as a function in a global include.
Neil
> -----Original Message-----
> From: Jeffry Houser [mailto:[EMAIL PROTECTED]]
> Sent: 01 June 2004 15:57
> To: [EMAIL PROTECTED]
> Subject: Re: [CFCDev] UDF in a CFC or Include?
>
>
>
> I only use a CFC if I have a need to encapsulate data and
> functionality.
> I only put functions in a CFC if they are specifically
> related to that
> CFC's data.
> I do not use CFCs as a generic "function library". I
> understand it is
> more efficient to put generic functions in a cfm file and include it,
> therefore you do not have the overhead of creating the CFC instance.
>
> Based on other responses, perhaps my view of CFCs is unique.
Jeffry Houser, Web Developer, Writer, Songwriter, Recording Engineer
<mailto:[EMAIL PROTECTED]>
--
AIM: Reboog711 | Phone: 1-203-379-0773
--
My Books: <http://www.instantcoldfusion.com>
Recording Music: <http://www.fcfstudios.com>
Original Energetic Acoustic Rock: <http://www.farcryfly.com>
