On 1/12/06, Cliff Meyers <[EMAIL PROTECTED]> wrote: > You're right, my bad. But given that the use of scopes is so > prevalent in every other area of CF I'm surprised the language design > team decided against providing a local scope inside of the CFFUNCTION > block. I don't really have a problem with "var" (and I use the "local > pseudo scope anyhow") but it just feels a little out of place.
I suspect that since CF5 introduced cfscript-based UDFs they took their cue from JavaScript etc that requires users to use 'var' to introduce local variables - making the (reasonable) assumption that CF developers would be somewhat familiar with JavaScript and there was no benefit to making CF UDFs too different. The <cffunction> tag just followed the lead of CF5... -- Sean A Corfield -- http://corfield.org/ Got frameworks? "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]
