> We're right in the throes of this, too. We've been operating under
> the understanding that using Duplicate() was necessary ONLY when dealing
> with complex variables.
>
> Thus, <cfset request.variablename = session.variablename>
> would work fine as long as session.variablename is not complex.
>
> NOT SO, says MM Tech Support. Seems like cfset ALWAYS sets a pointer
> rather than making a copy when dealing with shared-scope variables
> (session, application, server).
There are three possibilities.
1. You misunderstood what MM tech support said, or
2. MM tech support misunderstood what you were asking, or
3. MM tech support needs to implement drug testing.
It's very easy to test the above statement.
<cfset Application.bar = "baz">
<cfset Variables.bar = Application.bar>
<cfset Application.bar = "foo">
<cfoutput>#Variables.bar#</cfoutput>
If the variable within the Application scope was passed by reference to the
local scope, the output should be "foo", but when I ran it, it was "baz".
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
