Chad
My understanding is this:
caller scope is the 'variables' scope of the page/file that calls the
custom tag.
so cfm -> custom tag = caller scope is cfm variables scope
cfm -> cfc -> custom tag = caller scope is cfc 'variables' scope.
in your case:
cfm -> custom tag -> custom tag = caller scope should be scope of the
last custom tag that called this tag in the stack.
attributes scope is the scope of any variables passed as 'attributes' to
a custom tag / cfmodule.
if you want a scope that will be global to all recursions, try Request
scope.
Pat
Chad Renando wrote:
Hey all. I am still hacking my way through the custom tag thing, and
was wondering if someone could shed some light on the whole caller and
attribute scopes.
I have some nifty recursion going on in my custom tags. Do I need to
scope my variables as caller in order to maintain them through each
iteration of the tag? Specific areas where I have run into issues are
in the creation of arrays.
Is there any issue if I just declare everything as caller, if I am
careful with my naming conventions? If I set something as a caller,
can I then access it using the variable scope outside of the tag?
Cheers,
Chad
who is considering scoping his food as breakfast.eggs, lunch.fries and
dinner.potatoes
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
