I think the premise is that if you cfoutput the whole page, the whole page has to be parsed where as if you cfoutput selected parts there is less work for the page processor to do.
I tried this today for a reasonably complex page to see it would make a difference. Initial findings are that it did but the difference wasn't big. Would be interested to hear other peoples experiences with this.
Cheers, Pete (aka lad4bear)
----Original Message Follows----
From: "Nolan Erck" <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: <[email protected]>
Subject: RE: [CFCDev] LINT like tools for coldfusion?
Date: Tue, 14 Jun 2005 17:20:57 -0700
>>>* Too much (how much is too much?) code within cfoutputs
I've never heard of this before, and I've seen just as many pages that
turn <cfoutput> on/off as needed, as I have pages that turn it on once
at the top of the page and then at the bottom but nowhere else. How is
"too much code within cfoutputs" an item we need to avoid? This is new
to me. I thought it was mostly a personal preference.
Nolan Erck
Web Developer/Programmer
Schools Financial Credit Union
(916) 569-5409 Office
(916) 569-2024
Fax
www.schools.org
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Haikal Saadh
Sent: Tuesday, June 14, 2005 5:05 PM
To: [email protected]
Cc: Andrew John Rasmussen; Patrick James Simon; Ralph Vernon Bebendorf;
Aneesha Bakharia
Subject: Re: [CFCDev] LINT like tools for coldfusion?
Maybe we could get started by having a Wiki or something where we could
start off by contributing sets of rules that such a framework would look
for? There are a lot of sites out there with this information, albeit
scattered around everywhere. And of course, it's hard to judge which
versions of CF they apply to, as shown by the number of "Is this true
for version X" type of comments these pages attract,
Off the top of my head, I would suggest:
* Un-var-ed variables in function
bodies
* Not using cfqueryparam.
* Warn when scopes locks are used (as opposed to named locks)
* Too much (how much is too much?) code within cfoutputs. Or <cfoutput
query="">
* Suggest <cfsavecontent> rather than <cfset> when dealing with html.
(Not really any danger, but it's a lot more readable, and cfeclipse
likes that well formed markup better).
Of these, the first four have given us a _lot_ of grief, so it would be
good if it was easy to avoid making these mistakes in the future.
Paul Hastings wrote:
> Stuart Miller wrote:
>
>> I'd be interested in a tool like this even if it only checked
function
>> bodies for non var declared variables. Notoriety awaits anyone
willing
>> to build it!
>
>
> i was just about to say the same thing. that kind of tool would go
a
> long way towards building more stable apps.
>
>
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email to
> [email protected] with the words 'unsubscribe cfcdev' as the subject
> of the email.
>
> CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
> (www.cfxhosting.com).
>
> CFCDev is supported by New Atlanta, makers of BlueDragon
> http://www.newatlanta.com/products/bluedragon/index.cfm
>
> An archive of the CFCDev list is available at
> www.mail-archive.com/[email protected]
>
>
>
--
Haikal Saadh, Applications Programmer
Teaching and Learning Support Services
K405, Queensland University of Technology, Kelvin Grove Campus
[EMAIL PROTECTED], 3864
8633
CRICOS No. 00213J
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of
the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
The information contained in this e-mail is confidential and may contain privileged information exempt from disclosure under applicable law. The information is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, employee, or agent
responsible to deliver it to the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please delete the message from your computer and immediately notify the sender by telephone (you may call collect) at 916-569-5400 or by e-mail to [EMAIL PROTECTED] Thank you.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
