As much as we've all been arguing about this tag, I think this was a
very productive discussion. Let's just rewrite it so it works for some
of the new ideas that are brewing.
I've got a lot of the changes people have requested already done, i'll
give it a once over and let you all see what i came up with in the
morning. It won't affect anything for everyone else and it'll be
slightly faster. The only *major* thing I'm changing that could have an
effect on your code is the variable #request.attributeslist#. With this
new version it's not necessary because it's all in the #attribute#
structure.
Steve Nelson
Hal Helms wrote:
>
> Yes, I'm seriously thinking about doing just that. Since a fuse knows what
> is coming into it and makes this explicit through its Fusedoc, it would
> never use a local variable with the same name as an incoming variable. That
> really is an unthinkably bad idea. In which case, remind me again why I need
> to have a form or URL variable put into another scope other than the local
> scope.
>
> I'm not suggesting you'll agree with me. I find that in discussions of this
> sort, positions mostly get solidified but minds seldom get changed. Once
> someone makes the first post staking out an opinion...well, it's pretty rare
> to have someone come back and say, "Gee, I was wrong. I see your point."
>
> What I *am* suggesting is that we modify FormURL2Attributes so that people
> of different opinions can use the same tag. That seems to me a pretty
> reasonable plan.
>
> Hal Helms
> Team Allaire
> [ See www.halhelms.com <http://www.halhelms.com> for info on training
> classes ]
>
> -----Original Message-----
> From: Nat Papovich [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 23, 2001 8:09 PM
> To: Fusebox
> Subject: RE: Musings on Attributes (was Best Practices...)
>
> 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
