@Adam -- i am going to ignore your rather bold sweeping statements as i
believe they were made in the heat of the moment and bore from
frustration more than anything with no ill intent in mind. Matt and
Peter have addressed those.
## Issue 1: Dynamic Expressions
Here is a perfect example of what you call a "bug" but really could be
argued that Adobe should never really be allowing this in the first
place. This is a classic example of where Adobe have so many
inconsistencies with their language, that it makes it hard for the
developer let alone the alternative engines that try to mimic this
behavior. We have such a list of bizarre sh*t that we are still
scratching out heads wondering "why".
So the rub here is: #q.id eq arguments.id# inside a string.
Personally, if i was wanting that output in the string, i would never
have written like that in the first place, i would have written it using:
Evaluate("q.id eq arguments.id")
This is what the Evaluate() function was designed for. #..# is for
variable output.
Interestingly, this is only a bug when you include it as a parameter; if
you do the same with CFOUTPUT it works fine. So there is a little issue
there that we'll address.
## Issue 2: cfreturn + cfoutput oddity
Well spotted, and this has now been fixed. Can't really argue on
turnaround a time for that now can you? less than 12hrs, bug accepted,
fixed, and released --- and that is even after a rant! ;)
Keep them coming Adam. Everything reported is making it better and
stronger for everyone.
Adam Cameron wrote:
And the second bug is with this line:
<cfset arrayAppend(aDebug, "THIS SHOULD WORK TOO (but doesn't))!
currentRow: #currentRow#. #q.id# eq #arguments.id# = #q.id eq
arguments.id#")>
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
online manual: http://www.openbluedragon.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
