Awesome, this is good to know... Doesn't change my plans to convert everything to use the attributes scope -- the lack of it was just more encouragement for me to tighten up some of my old spaghetti code from '97-98...
> Variable scoping has been fixed in the BlueDragon 3.0.1 > service pack (to > be released within two weeks) to match CF5/MX. You can > then omit > variable prefixes and scopes will be searched in the > expected order. > Having said that, you should always use variable prefixes > (in CF5, CFMX, > and BlueDragon) for performance reasons. > Vince Bonfanti > New Atlanta Communications, LLC > http://www.newatlanta.com >> -----Original Message----- >> From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]] >> Sent: Monday, October 14, 2002 6:48 PM >> To: CF-Talk >> Subject: RE: BlueDragon (was RE: How is CFMX J2EE >> implemented?) >> >> >> I've been working _toward_ making my cms application >> compatible with BlueDragon myself... My biggest issue has >> actually been one of poorly scoped code on my part, using >> #pageid# to grab from either the form or url scope ( hey, >> I >> started all of this 5 years ago, when I first got into >> CF, >> what do you expect :) ... The comparison doc does mention >> that you can't reference form and url variables as if >> they >> were local variables, so you have to prepend either form >> or >> scope to your variable name if for no other reason than >> to >> set your local variable. Form and URL are also a combined >> scope on BlueDragon, so form.myvar and url.myvar are the >> same >> thing, which I think is a great idea, although I could >> see >> where it could cause problems in some rare applications >> where >> the scope of the variable is important. In any event, >> it's >> slow going, but I think I'm getting there... >> >> I'm using the FuseBox trick to copy all the form and url >> variables to the attributes scope and then using the >> attributes scope for all my passed variables. >> >> <cfparam name="attributes" type="struct" >> default="#structnew()#"> <cfset temp = >> StructAppend(attributes,form,false)> >> <cfset temp = StructAppend(attributes,url,false)> >> >> This is great in my case because once I get all my poorly >> scoped local variables fixed up, this will work on both >> CF >> and BlueDragon -- and users on BlueDragon and comment out >> or >> remove the second <cfset> statement to get a small >> performance boost. At some point I'll probably wind up >> checking the server provider and putting a <cfif> >> statement >> around the second >> structappend() so that the comment will be unnecessary. >> >> I still have some questions about wddx, but I'm mostly >> convinced / hopeful it will work in both environments. >> >> Isaac >> Certified Advanced ColdFusion 5 Developer >> >> www.turnkey.to >> 954-776-0046 >> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~~~| > Archives: > http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 > Subscription: http://www.houseoffusion.com/index.cfm?sideb > ar=lists&body=lists/cf_talk > FAQ: http://www.thenetprofits.co.uk/coldfusion/faq > This list and all House of Fusion resources hosted by > CFHosting.com. The place for dependable ColdFusion > Hosting. Isaac Certified Advanced ColdFusion 5 Developer www.turnkey.to 954-776-0046 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
