Hi Richard,
FusionDebug uses the expression evaluator of the underlying ColdFusion
engine to watch/inspect and set expressions.
Although the syntax is supported in cfscript it isn't supported by
ColdFusion's evaluation engine, for example:
<cfset x=evaluate("1 != 2")>
will return the follow error in ColdFusion:
Invalid CFML construct found on line 1 at column 3.
ColdFusion was looking at the following text:
!
The error occurred in C:\test\test.evaluate.cfm: line 1
1 : <cfset x=evaluate("1 != 2")>
Whereas
<cfset x=evaluate("1 neq 2")>
Will return YES
We made a conscious decision to use the underlying engine evaluator to
make sure the expression syntax that is supported by the engine will
work in FD. A workaround is to replace the Javascript operators with
CF's evaluate operators (gte, neq, eq, etc...) by editing or adding
the expression in that way. I have tracked a ticket for this against
FD, but really we need the underlying engine to iron out this
inconsistency and you might want to track an issue with the CF bug
tracker to add support for the CFScript/Javascript operators to the
evaluator in
http://cfbugs.adobe.com
Cheers,
Darren