Oh, one more reason for not using Evaluate() - structures can hold keys that
aren't CF-Variable-Name-Compliant and Evaluate() can't handle them. For
example, numeric struct keys will generate an error with Evaluate():
The code:
01: <CFSET foo=StructNew()>
02: <CFSET quux=12345>
03: <CFSET foo[quux]="b">
04: <CFTRY>
05: <!--- these work fine --->
06: <CFSET brick=foo[quux]>
07: <CFSET brick=foo["#quux#"]>
08: <!--- this will break --->
09: <CFSET brick=Evaluate("foo.#quux#")>
10: <CFCATCH><CFOUTPUT>#CFCATCH.Message#</CFOUTPUT></CFCATCH>
11: </CFTRY>
The output:
An error occurred while evaluating the expression:
brick=Evaluate("foo.#quux#")
Error near line 9, column 13.
An error has occurred while processing the expression:
foo.12345
Invalid parser construct found on line 1 at position 4.
ColdFusion was looking at the following text:
.
Invalid expression format. The usual cause is an error
in the expression structure.
-Rick
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
