PERFECT!
Roger has hit the nail on the head here. You new-schoolers who want to send
all form and URL vars to local scope are missing a major thingy here. Even
if you don't ever want to know whether a variable came from a previous
user-click (form or url), that doesn't mean that the rest of us have to put
up with such nonsense. Leave formurl2attribs as it is. You can rewrite it
for yourself, let monkeys fly out of your butt, I don't care. Just don't
make the "standard" a bad idea.
Hal - are you seriously interested in using the variables scope for all form
and url vars? I hope my Mini Halbert doesn't think that, else I'd have to
"put him down". That's about as dangerous as converting them all to request
scope, which we discussed a few months ago...
NAT
> -----Original Message-----
> From: Roger B. [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 23, 2001 2:05 PM
> To: Fusebox
> Subject: RE: Musings on Attributes (was Best Practices...)
>
>
> > What they
> > should have done is just copy everything to the local scope (variables).
>
> Patrick,
>
> Nah... then they would end up losing their status as "incoming" variables.
> In my code, "attributes" means something significant: that
> variable made it
> into the mix via an URL, a form, or a custom tag attribute. Simply dumping
> it into the variables scope would be throwing away useful
> information, IMO.
>
>
> --
> Roger
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
