The only issue I have with having it in global scope and just "using" it in the tag is that it does not look cleaner to me. You will have other attributes passed into the tag and one var of UDFs with global scope (app/request) will be directly referred to in the tag. I can't think of a reason why it would bite in buttocks. I guess, it's a matter of preference.
On Wed, Sep 2, 2009 at 4:41 PM, Rick Root <rick.r...@webworksllc.com> wrote: > > To be honest, I tend to put "utility functions" into a component > called udf.cfc and then load that component into a shared scope > (application or server) on initialization. That way they're always > there in memory. > > I don't like the idea of passing functions into a custom tag though it > would certainly follow the rules of "encapsulation" a bit more, either > way seems like a violation to me, really. But then, I don't think > I've used a custom tag in ages either. > > -- > Rick Root > CFFM - Open Source Coldfusion File Manager > http://www.opensourcecf.com/cffm > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325966 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
