>> In fact, is it worth reporting as a bug, as I'm on the <mummble> beta ? >> Would it be better to have all variables thread-safe (var'ed) by default ?
give up now, methinks. within a function <cfset var qry = ""> makes perfect sence since there really isn't any diff between creating a var and assigning a value (just using CFSET without the var, that is). I mean, how can you tell if you're accessing a local variable or changing a "global" one with the same name? ie: if CF had a specific command for creating variables, then it wouldn't be an issue (eg: in VB) Dim myString as string '-- declare and initialise as null myString = "hello" '-- assignment so how about changing "CFSET" so that "var" creates and initialises anywhere it's used - not just in functions? then throw an error if CFSET was used if it wasn't "var"d first. that way it'd be closer to what lots of other languages do. however, if you really want to improve things, I think you'd get much more go with having a (real) non-inheritable private scope in CFC's (keeping in mind that a CFC's variables scope is more like a protected scope). just a thought barry.b -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
