On Fri, Sep 3, 2010 at 1:32 PM, Alan Holden <[email protected]> wrote:
> Also, is it a performance hit to make use of CF's loose type Boolean
> feature?
> (where any int above 0 is automatically considered true)
>
> Thus shortening your test to:
>
> <CFIF find("@","#form.recipient_user_name#")>
>
I doubt that would impact performance at all. I tend to explicitly do eq 1
or neq 0 since that's actually what find returns (a number, not a boolean)
but that's probably me being overly anal again. ;-) In some cases depending
on the code it can definitely make it less confusing to read/grok if the
numbers are there.
Bottom line is it's a stylistic thing and I'd be shocked if by the time
that's compiled down it made one ms difference in performance.
--
Matthew Woodward
[email protected]
http://blog.mattwoodward.com
identi.ca / Twitter: @mpwoodward
Please do not send me proprietary file formats such as Word, PowerPoint,
etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
official manual: http://www.openbluedragon.org/manual/
Ready2Run CFML http://www.openbluedragon.org/openbdjam/
mailing list - http://groups.google.com/group/openbd?hl=en
