Well, I'm going to pretend to speak for the original poster, but in general, the answer is no. You would only use cfparam if you really want your logic to be:
"If foo is not defined, set it to...." There is nothing wrong with: <cfset foo = ""> Nor is there anything wrong with: <cfparam name="foo" default=""> But you should use the line that makes sense for your app. If you intent is to create an empty string, <cfset foo = ""> is not only correct, but faster and safer. ======================================================================= Raymond Camden, Principal Spectra Compliance Engineer for Macromedia Email : [EMAIL PROTECTED] Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: Neil Clark - =TMM= [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 24, 2002 7:58 AM > To: CF-Talk > Subject: RE: Reg Expr help. > > > Should u not use <cfparam> instead of <cfset problemFields=""> for > setting an empty variable in the first instance.? > > > > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
