I am looking to make some variables in a cfc available to all
the functions in that cfc. I used to do this with properties, but
just discovered a problem with that approach. Now I am trying
normal variables, but I find that not all of them keep their value.
The pattern appears to be, if the variable was set to an arguement
it loses it's value, otherwise it keeps it.
For example
Calling template:
args = structNew();
args.StartDate = "2006-09-01";
args.EndDate = "2006-09-01";
abc = CreateObject("component","BlocksAndClosures");
x = abc.init(argumentcollection = args);
z = abc.blocks();
-------------------------------
Start of cfc
<cfscript>
WhatToUse = "not set";
StartDate = "1990-01-01";
EndDate = "1993-01-01";
x = true;
</cfscript>
----------------
init function code
StartDate = CreateOdbcDate(arguments.StartDate);
EndDate = CreateOdbcDate(arguments.EndDate);
WhatToUse = "something else";
<cfdump var="#variables#">
-----------------------
blocks function code
<cfdump var="#variables#">
------------------------------------
When I dump the variables at the end of the init function,
all the variables have the new values. That is to be expected. When
I dump them in the blocks function, WhatToUse now equals "something
else" which came from the init function. However, the two date
variables have the 1900 and 1993 values which appear to mean that
they were reset.
I can work around this but does anyone know why not all the
cfc variables behaved the same when the block function was
called?
Could you be getting a scope collision with the arguments variables and your global variables? What happens if you rename the arguments or the global vars? I've gotten the CFC global variables thing to work before, but I usually make sure that the global variables name differ from my local or input variables.
Renaming the global variables made it work. Thank you very much. I take back half the bad things I said about you.
Renaming the global variables made it work. Thank you very much. I
