RE: #request.variable#

[Roger B.]

> PART 3: Dealing with anti-CFOUTPUT code, such as CFMAIL
> Encapsulate all code by STARTING with a </CFOUTPUT> and ENDING with a
> <CFOUTPUT> to restore the CFOUTPUT nest.

Alan,

That's where the idea comes apart for me. I just can't see spreading the two
halves of a tag pair across multiple templates. There's something
inherently... "messy" about it, if nothing else.

Now, I could perhaps see something like this:

<CFCASE value="foo">
        <CFINCLUDE template="qry_dothis.cfm">
        <CFOUTPUT>
                <CFINCLUDE template="dsp_showstuff.cfm">
                <CFINCLUDE template="dsp_morestuff.cfm">
        </CFOUTPUT>
        <CFINCLUDE template="act_sendmail.cfm">
</CFCASE>

....but at that point, you might as well just put the output wrapper in the
individual dsp_ files and keep the CASEs clean.


--
Roger


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists