Re: [CFCDev] Typing Arguments of a Function

[Robert Munn]

Keep in mind that UDFs are not the same as CFCs. CFCs can be instantiated and persisted and act generally like objects, whereas UDFs by themselves are purely procedural. That said, the technique Nolan mentions is a workable way of doing things. I switch between tags and script myself.

On 7/19/06, Jimmy Glass <[EMAIL PROTECTED]> wrote:

Morning,
Personally, I feel that CFSCRIPT code is much prettier than a tag based CFC.
But, my intent is not to spark a debate on the elegance of using tags. In
instances where my functions require a tag, I generally use a CFC that I've
built which contains functions that interface with the tag. CFQUERY, CFDUMP,
etc. I'm sure this is a rather common technique.

What I do like about the CFFUNCTION/CFARGUMENT tags are the ability to
explicitly define the return type and output of a function, and the data
types of the arguments. To my knowledge, this is not possible when defining
a function w/ CFSCRIPT.

Does anyone have a work around, or a way of accomplishing this in CFSCRIPT?

Thanks,
Jimmy G






----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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/cfcdev@cfczone.org

--
---------------
Robert Munn
www.funkymojo.com ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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/cfcdev@cfczone.org