On Wed, 16 Mar 2005 13:21:10 -0000, Robertson-Ravo, Neil (RX) <[EMAIL PROTECTED]> wrote: > Sean, can you give a case where it is a) unnecessary and b) required with > regards to dynamic processing - I think this would help clarify the > situation.
No, every case I've seen can be coded without evaluate(). > I used to avoid it like the plague on advice of others but really I haven't > really found any huge performance hit with it and in some cases you have to > used it when evaluating data - is there some hidden way to avoid using > Evaluate? Show me a case where you think you really need it. > If its not required or not advised when it comes to use - why is it still in > the CF dictionary and not deprecated and been replaced with a faster more > efficient means of dynamic evaluation. I think a lot of code relies on evaluate() - pre-MX you couldn't just mess with scopes as if they were structs so you needed it back then. >From MX onward, there is already a "faster more efficient" way to avoid evaluate(). I would like to see it deprecated but it isn't my choice to make. -- Sean A Corfield -- http://www.corfield.org/ Team Fusebox -- http://www.fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
