See, I thought my argument was rhetorical and that, OF COURSE, you would
allow for that, but you're holding fast for purity and you gotta love that!!
Hal Helms
Team Allaire
[ See www.halhelms.com <http://www.halhelms.com> for info on training
classes ]
-----Original Message-----
From: BORKMAN Lee [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 2:32 AM
To: Fusebox
Subject: RE: Surveying the community
Well, yeah, I do have a problem with that. I'm going back top your article
on Conquering Complexity (was that the title?). The rules were simple
enough that I can give them from memory:
Rule One: No fuse shall call another fuse; EXCEPT...
Rule Two: A fuse may sometimes call a "FuseFunction" as a customtag,
provided that:
- the fusefunction returns to the calling fuse; and
- fusefunction CF_XXX returns a variable "XXX" to the calling fuse.
That was about it. Rule 2 was basically a compromise to allow for extreme
circumstances where the pure application of Rule One just wouldn't work.
So I could live with this:
<!-- FormattedTime.cfm -->
<CFSET caller.FormattedTime = "#TimeFormat( now(), 'h.m.' )#">
<!-- myFuse.cfm -->
<cf_FormattedTime>
#FormattedTime#
This keeps the potentially escalating connections from running away,
treating the fusefunctions as close as we can to "normal" functions.
Or was this some other Hal Helms? Dagnabbit! Mate, I KNEW I had the wrong
guru all along! Bizarro-Hal's new definition of a fuse sure leaves me out.
Most of my so-called fuses don't accept a returnfuseaction at all. That's
an optional extra I use when I see a need - otherwise, my fuses just have a
beginning and an end (very few have a middle). Then they simply return.
It's up to the calling FuseBox to decide what to do next. That's its job.
Otherwise it gets old and lazy like me.
Leeb.
-----Original Message-----
From: Hal Helms [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 10 April 2001 16:10
To: Fusebox
Subject: RE: Surveying the community
But what is a fuse? Surely, you don't have a problem with this?
<!-- incShowTime.cfm -->
#TimeFormat( now(), 'h.m.' )#
<!-- myFuse.cfm -->
blah
blah
<cfinclude template="incShowTime.cfm">
or
<cf_incShowTime>
blah
blah
//
A couple of years ago, I came up with the 10 rules of Fusebox, one of which
was this:
No fuse may call another fuse.
But what is a fuse? Is incShowTime.cfm a fuse? If so, we're gonna be writing
the same code over and over and...not much reuse there.
I came up with this definition:
A file is a fuse if and only if it accepts an exit fuseaction. Otherwise,
it's not a fuse. This lets you have inc files (or block files I think Steve
calls them), Fusefunctions, query files, etc.). The important thing is that
the fuse always gets back control.
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
