Yeah, but this presumes that you already know everything, at the design
stage, about the possible environments in which your fuse will be called.
And that surely precludes the fuse from being re-used in different
circumstances.... Oh dear, I'd love to re-use that fuse over HERE, but it
blows away variable X, Y and Z!!
-----Original Message-----
From: Hal Helms [mailto:[EMAIL PROTECTED]]
Well, the whole idea of XFB is that you DO know EXACTLY what vars you're
getting in before you write the first line of code (via Fusedocs). I treat
ALL scopes as a single entity in thinking about naming, so I would not have
a local variable with the same name as a request variable, an attributes
variable, etc. I find this is just integral to the way I write code and I
would be very uneasy with relying on scopes to differentiate variable names.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
