Bob brings up a great point below:

> One other thing that comes to mind about simply using the variables scope
> for everything, rather than attributes or another "made up" scope (using a
> structure) is that I commonly use a variation on the CF_REUSEFORM
> tag, which
> depends on there being values in two different scopes, "variables" and
> "attributes".  If I was to use the "variables" scope to replace the
> "attributes" scope I'd have to rethink the way this tag is being
> used (which

I oftentimes have many routines that do different things depending on the
existance of a variable in the attributes scope, at the same time, the same
variable name lives in the variables scope. Copying all form and url vars to
the local scope would mess up this beautiful system.

NAT


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to