-----Original Message-----Fair enough Aaron. In that light, I'll say that, in my opinion, the vast majority of developers would find it harder to read.
From: Brian Kotek [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 18, 2006 4:17 PM
To: [email protected]
Subject: Re: [CFCDev] CFINVOKE vs. Evaluate
regards,
Brian
On 5/18/06, Aaron Rouse <[EMAIL PROTECTED]> wrote:While I agree with the harder to read statement I do feel the need to point out that it is a personal opinion. I once showed someone a solution that used the brackets and had someone comment how that is hard to read and they prefer the method that I believe used either Evaluate or SetVariable.
On 5/18/06, Brian Kotek < [EMAIL PROTECTED]> wrote:I think we might all be lapsing into pedantry on this subject, but I just don't agree. If you know that you can easily avoid using evalute() and yet you choose to use it anyway, then that's just lazy. I can follow the "just make it work now" idea, and I agree in general. But if you deliberately choose to write:
<cfset theValue = evaluate('form.' & fieldName) />
instead of
<cfset theValue = form[fieldName] />
knowing full well that the first one is almost guaranteed to be less efficient (not to mention harder to read), then that's just plain wrong.
On 5/18/06, Nolan Erck <[EMAIL PROTECTED]> wrote:I don't like this point (and I'm really not trying to single out Brian at all - this is just the point where I felt like chiming into the conversation). Yes evaluate() is slow, but because someone uses "feature A" instead of "feature B" of a language, I disagree that it always is because of a lack of understanding of features.
I've written apps in the past, and in keeping with the "make it work now, make it fast later" ideals (which sometimes have to be followed, depending on your work environment and schedule...Doug are you out there? Back me up here! :) ), I will write code in the first way I can think of that gets the job done. Sometimes things are out of my control, and I _ have_ to wait for version 2 before I can go in and remove calls to evaluate(), and other poorly/quickly written sections of code. And if I'm writing a library that I need to get _ working_ now, I know there are spots that I've used evaluate() to get something done.
Everything has it's place...
----------------------------------------------------------
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).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
--
Aaron Rouse
http://www.happyhacker.com/ ----------------------------------------------------------
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).
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).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
This electronic communication, together with any attachments, may contain information that is legally privileged, confidential or otherwise private. 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, please be aware that any disclosure, copying, distribution or use of the contents of this communication or any attachment is strictly prohibited. If you have received this communication in error, please immediately notify the original sender and delete the received information from your system. Thank you.
