> -----Original Message----- > From: Adrian Lynch [mailto:[EMAIL PROTECTED] > Sent: Friday, April 04, 2003 9:54 AM > To: CF-Talk > Subject: RE: cfparam > > > I understand what it's doing, but I'd rather it worked like > the example I gave than throw an error.
Of course if it did this thread would have been created by somebody else wishing it worked the other way. ;^) You can't please everybody so CF's core philosophy has always been to make things work the way most people would use it most of the time. It's part of it's abstraction-of-complexity mission. When you wan't to do something different or more complex CF provides many avenues of extension for you. I suppose that a new attribute - something like "ApplyDefaultForTypeMismatch" but named better would solve it... But that would require a change to the language. A simpler option considering is to create a CustomTag or UDF that does just what you described and use that instead. By using the "Is()" functions inside a case statement with try catch this should be very easy. Then you'd call <CF_ParamPlus> (or maybe even <CF_ParamTheWayIDamnWellWantIt> or, my favorite <CF_ParamALamaDingDing>) instead of <CFPARAM>. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
