In your particular case, then yes, this makes sense. And for variables in application scope, this is probably good practice. I just wanted to point out that what is right for one situation is not always right for all situations. But that's kinda like stating the obvious to developers isn't it?... <grins>
Shawn Grover -----Original Message----- From: Chris Norloff [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 11:58 AM To: CF-Talk Subject: RE: cfparam vs. cfif/isDefined/cfset <snip> For example: we maintain 5 server locations, some secure and some not. Some of the site-specific information is contained in application scoped variables. We either set them all or we don't set any. Thus, we check for one of them, and if it doesn't exist then set all of them. </snip> ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. 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
