> My understanding is that it fixes a bug in CFMX 7 (and earlier CFMX releases) where the second 'e' would have ended up in 'variables' scope (and thus not been thread-safe).
I can recall this being the case in 6.1, but doesn't *seem* to be that way in CFMX7.0 (provided you VAR the exception variable, natch). > CFMX 7.0.1 now creates a new implicitly local variable for catch() so that it > is thread-safe. Right. The fact that it doesn't really seem broken in CFMX7 notwithstanding, my approach to this would be the same as with any other variable... You create the local variable with the VAR keyword at the top of the function. Why the different approach here? Whilst on the subject of 7.0.1... Was there a beta programme for it? The first I heard about it was when it was released :-( -- Adam -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.361 / Virus Database: 267.12.4/146 - Release Date: 21/10/2005 This email contains confidential information. If you are not the intended recipient of this email, please notify Straker Interactive and delete the email. You are not entitled to use it in any way. ---------------------------------------------------------- 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). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
