Curiously, I do it the exact opposite way:

<cfset variables.myVariable = "fubar" /> <!--- ensure that I am
setting in the variables scope, because there could be a 'myVariable'
in another scope --->

<cfoutput>#myVariable#</cfoutput> <!--- I have just guaranteed that I
have variables.myVariable, there is no possibility (afaik) that I
could be refering to another 'myVariable'. --->

However, I should probably scope both.

Dominic

On 18 May 2011 19:26, Aaron Rouse <aaron.ro...@gmail.com> wrote:
>
> This is my outlook although I do not do something like:
>
> <cfset Variables.strBlah = "something" />
>
> instead I do:
>
> <cfset strBlah = "something" />
>
> But I always would do:
>
> <cfoutput>#Variables.strBlah#</cfoutput>
>
> or
>
> <cfif Variables.strBlah IS "something">
>
> Seems to me that is what the original OP is asking about but perhaps I am
> reading too much into it based upon what I do.  This is all in reference to
> just straight CFM pages.
>
> On Wed, May 18, 2011 at 12:40 PM, Maureen <mamamaur...@gmail.com> wrote:
>
>>
>> ALWAYS SCOPE!!!!!
>>
>> Especially if someone else might have to maintain the code someday.
>>
>> On Wed, May 18, 2011 at 9:51 AM, Eric Roberts
>> <ow...@threeravensconsulting.com> wrote:
>> >
>> > We had a discussion at work as to whether or not we should scope local
>> vars
>> > with the "variables." scope since that is implied in a cfset.  One camp
>> says
>> > it is not needed because of the implicit scoping when using cfset...the
>> > other camp says it is better to tack on "variables." and make it explicit
>> > for security and readability.  Any thoughts?
>> >
>> > Er
>>
>>
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344640
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to