No flame from me!!
Yes, it can get ugly.
The best solution to Michael's original problem would have been to
explicitly state the FORM scope:
<CFSET FORM.pattern_Name = replace(FORM.pattern_name, 'me', 'you')>, etc.
I have spent too much time reading that piece on unmaintainable code. ;-)
Lee (Bjork) Borkman
http://bjork.net ColdFusion Tags by Bjork
-----Original Message-----
From: Jaime Garza [mailto:[EMAIL PROTECTED]]
I come from a C,C++ background so I usually like to keep my structures more
obvious.
the fact that #pattern_name# in cold fusion is a two step search bothers me.
It first looks for a global pattern_name and then for form.pattern_name.
Yuck!
...
This looked good to me at first, but then cf is really doing an assignment
to a global bar, not to the query's bar. CF is not very clear on their
scoping rules. As a rule, keep it explicit, and not mix variables as you
do.
(Here it comes the flame... I am ducking already.)
...
IMPORTANT NOTICE:
This e-mail and any attachment to it is intended only to be read or used by
the named addressee. It is confidential and may contain legally privileged
information. No confidentiality or privilege is waived or lost by any
mistaken transmission to you. If you receive this e-mail in error, please
immediately delete it from your system and notify the sender. You must not
disclose, copy or use any part of this e-mail if you are not the intended
recipient. The RTA is not responsible for any unauthorised alterations to
this e-mail or attachment to it.
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
