is there any reason why the attributes "scoped" variables are defined as straight "<CFSET attribute.<var>" (well..using setVariable, but you get my meaning) as opposed to in an "attribute" struct like FORM and URL scoped variables?
I'm writing an app where i need to loop through these vars and ended up just copying/pasting what was already done in formurl2attributes and storing them in a struct (well..actually wrote it as a UDF, but that's besides the point). I'm just curious why the break from the apparent standardized approach that MM took regarding scopes. Perhaps this is addressed in the specification (or updated in v3 since i'm using 2), but my computer is currently not liking pdf files (locks up), and i don't have word installed. :) Bob ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
