If you have a method that is expecting an array as an argument, where you will be looping over that array, wouldn't you want to make sure its actually an array before you try to loop over it? By setting type="array" CF takes care of that for us. Otherwise, you would need to add a <cfif> to the method to verify that it is indeed an array that was passed in.
On Wed, Jun 2, 2010 at 8:36 AM, Zaphod Beeblebrox <zaph0d.b33bl3b...@gmail.com> wrote: > > I may be missing something, but I can't find a reason for this? I can see it > where you have a compiled language as it would throw an error at compile > type, but for a dynamic language what could the benefit be? > > > On Jun 2, 2010, at 6:48 AM, Larry C. Lyons wrote: > >> its good for >> development, but really the return type ought to be set for >> production. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:319992 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm