>Using a psuedo-scope means you always have to dereference >arguments using >the scope qualifier. Not using it means you can ignore the >arguments scope >(except for structKeyExists), not scope any local variables, >and never have >to worry about using the right scope anywhere. >
The only real reservation I have about that approach is that it makes it hard to read code without there there being some ambiguity in which variable is supposed to be referenced. Given that there are 6 implicit lookup scopes plus the cfquery loop scope and the function local scope, that could lead to some errors that are pretty hard to track down. If you always scope everything _except_ arguments and function local variables then I think it makes sense, but could still lead to unexpected behaviour after the code has gone through a few revisions. On the whole I think it's relatively unlikely that this would be a big issue in most applications though since it's essentially the same issue that we've had to deal with for years when not explicitly referencing the variables scope. Spike -------------------------------------------- Stephen Milligan Code poet for hire http://www.spike.org.uk Do you cfeclipse? http://cfeclipse.tigris.org ---------------------------------------------------------- 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]
