That is definitely true, however, it can also be undesirable, for example a
developer might want form submissions to only arrive via post and not get.
I prefer to try to code using scopes and typically use something similar to
this in the case you mentioned (one may note that this is copied from
fusebox's functionality):
Function setAttributes() {
attributes = StructNew();
StructAppend(attributes,'form',true);
StructAppend(attributes,'url',true);
}
By explicitly declaring I'm choosing to use have both scopes together, I can
remove that ambiguity, and explicitly declare which scope I want to have
precedence while I'm at it.
- Calvin
-----Original Message-----
From: Claude Schneegans [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 27, 2005 9:23 AM
To: CF-Talk
Subject: Re: Best practice question?
>>I believe that scoping is important and removed ambiguity
Right, however, in some circumstances, ambiguity may be a useful feature.
For instance, not specifying the form or url scope for a variable can
make a template work both as a form action or as an href called template
with parameters passed in the url.
--
_______________________________________
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam to this address: [EMAIL PROTECTED])
Thanks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:200128
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
