Well when I see your code I can see right off the bat that becuase there are quotes that you're setting it to a string. I think the pounds are an extra step, it's easier for to read, for me it's just as easy to read the quotes. To each his own.
Robert Everland III Dixon Ticonderoga Web Developer Extraordinaire -----Original Message----- From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 09, 2002 4:54 PM To: CF-Talk Subject: Re: Form.FIELDNAME - error!!!! I understand your point, but it is like saying periods clutter up pages in a book. If you have: <cfset variables.my_var = "#query.column#"> That tells me that there is a variable being set and it is a string <cfset variables.my_var = "query.column"> Am I setting my variable to the two words seperated by a period, query.column? or to a variable query.column? To each his own, but it makes more sense to me to see those pounds on the right hand side .. Plus reading a book with periods is easier too :) Paul Giesenhagen QuillDesign http://www.quilldesign.com SiteDirector Commerce Builder > I think that the # on the right side of the set operand is redundant. > > <CFSET my_var = #another_var#> > > or > > <CFSET my_var = another_var> > > There is only one thing for *another_var* to be: a variable. If you wanted > my_var to hold the string "another_var" you should quote the right hand > side: > > <CFSET my_var = "another_var"> > > So my .02 is that pounds just clutter up your statement. > > Reuben Poon > > > -----Original Message----- > From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 09, 2002 1:35 PM > To: CF-Talk > Subject: Re: Form.FIELDNAME - error!!!! > Importance: Low > > > Tim, > > I wouldn't call that bad practice, It should actually be called good > practice (at least in my book). You are setting a variable and the ## > around the variable show that it is a variable, makes for easier reading. > Now, ## on the set side would be considered bad practice. > > my .02 > > Paul Giesenhagen > QuillDesign > http://www.quilldesign.com > SiteDirector Commerce Builder > > > > Not sure if this is an error or just a bad practice, but you don't need > the > > # signs in your variable declaration (cfset) > > > > <CFSET var = ListGetAt(Form.FIELDNAMES, i)> > > > > works just fine. Also you don't need to generate that var at all you can > > just do a list loop like this: > > > > <CFLOOP list="#form.fieldnames#" index="formField"> > > #formField# = #evaluate(formField)# > > <CFLOOP> > > > > Tim Heald > > ACP/CCFD :) > > Application Development > > www.schoollink.net > > > > > -----Original Message----- > > > From: Chakka, Sudheer [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, May 09, 2002 4:16 PM > > > To: CF-Talk > > > Subject: Form.FIELDNAME - error!!!! > > > > > > > > > Hi, > > > > > > Can any one tell me what is the mistake in > > > > > > <CFLOOP FROM="1" TO="#ListLen(FORM.FIELDNAMES)#" STEP="1" INDEX="i"> > > > <CFSET var = #ListGetAt(Form.FIELDNAMES, i)#> > > > #ListGetAt(Form.FIELDNAMES, i)# = #Evaluate(var)# > > > <BR> > > > </CFLOOP> > > > > > > > > > I am getting the following error: > > > > > > An error occurred while evaluating the expression: > > > "#ListLen(FORM.FIELDNAMES)#" > > > > > > > > > Any help on this is appreciated. > > > > > > thanks, > > > Sudheer Chakka. > > > > > > > > > > ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm 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
