I hate trying to figure out whether an action is being caused because of a variable that could have been paramed, created by a query or sent in from a form or a url. Especially when I have to pick up an existing FB app, scoping everything in the attributes scope has usually made more work for me, not less.
On Thursday, June 19, 2003, at 04:15 PM, Bryan Love wrote: > For one, it adds definition to the code. It's easier to see what's > going on > when the FORM or URL scope is explicity used. > > For two, there are a few times when you'll have a page that could > accept a > variabl via form or url. In this case you MAY choose to leave the > variable > name unscoped so that either one will be picked up by the code, but > further > down in the same code you may need to distinguish between FORM or URL > to > determine a course of action. > > There are plenty more reasons hiding out there, but these are two I can > think of right now... I'm sure someone will berate me for even > mentioning > the second one, and to them I say "there is a time and place for > everything" > ;) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
