You can use CFEXIT METHOD="exittemplate" anywhere to abort the current
template, but not the request. I don't use it much, but it's occasionally
useful where you'd otherwise have to put an entire file (generally a FB
fuse) inside a conditional. I think it helps with readability to say "if
this isn't true, don't execute the fuse" at the top of the file, rather than
wrapping the entire content inside a CFIF block. This is a poor example,
but when the "big nastiness" is more than 30-40 lines, and has a lot of
nested conditionals or whatever, you start to see the benefit to
readability.
<cfif someTest>
<!--- big nastiness --->
</cfif>
Versus
<cfif NOT someTest>
<cfexit method="exittemplate" />
</cfif>
<!--- big nastiness --->
Cheers,
barneyb
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
> Sent: Tuesday, June 29, 2004 2:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [CFCDev] CFEXIT or CFABORT within CFFUNCTION
>
>
>
>
>
> Vince. As far as I know, CFEXIT only has application in
> custom tags. As
> for CFABORT, my feelings are that it should be allowed
> anywhere, and when
> it's encountered, all processing should halt. We use it
> almost exclusively
> for debugging.
>
> -Rob
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
