If it could possibly come in through some other scope then probably best to always copy it in from where it could come from and then reference that. For instance we have some pages that can refer to variables from the Form or URL scope. So we do something like this: <cfset StructAppend(FORM, URL, false) /> <cfparam name="Form.ID <http://Form.ID>" default="0" type="numeric" /> I know some people like to copy things into the REQUEST scope then reference them from that. I personally would avoid the not scoping technique, it can make for a nightmare when debugging things and more so when they are things someone else wrote.
On 7/5/05, Claude Schneegans <[EMAIL PROTECTED]> wrote: > > >>#form.email# or #email# > >>Are they interchangeable? > > If you use the first, it will work only if values are passed from a > form, if it is the case, it will be more efficient. > With the second option, the template can also accept values passed in > the URL, which can be useful in some cases. > > -- > _______________________________________ > 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:211154 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
