While I'll agree that the readability/maintainability factor is
important from a developer's viewpoint, that particular article was
specifically focused on performance and was merely pointing out which
functions were technically faster.
If one function is built to be faster than another functi
I'd be leery of something that says, "always".
Sometimes, it's OK to consider the readability/maintainability factor.
On Wed, Jul 15, 2009 at 2:08 PM, Eric Cobb wrote:
>
> According to this "Performance tuning for ColdFusion applications" post,
> you should always use compare() or compareNoCas
According to this "Performance tuning for ColdFusion applications" post,
you should always use compare() or compareNoCase() instead of the IS NOT
operator, and you should use listFindNoCase() or listFind() instead of
the IS and OR operators.
http://www.adobe.com/devnet/coldfusion/articles/cold
I have long been in the habit of using EQ and NEQ (and now moving to == and !=)
for numbers in all cases, since there is no such thing as 'sort of equivalent',
like there is with strings ('foo IS FOO' etc). For strings I use IS, unless
case is important, and then I use CompareNoCase().
~
= etc.
~Brad
Original Message
Subject: Comparisons - Your thoughts
From: Chuck Weidler
Date: Wed, July 15, 2009 1:52 pm
To: cf-talk
I was wondering what the community was doing with comparisons, like in a
cfif. I have done it many different ways. List below are just few
exa
I was wondering what the community was doing with comparisons, like in a cfif.
I have done it many different ways. List below are just few examples, and yes
I know that the Compare() and CompareNoCase() should be used for string
comparison and not numbers, but I have seen it done that way in
6 matches
Mail list logo
