Well - it is the same as any other language I've ever dealt with - You need to tell the compiler that these variables are only specific to the scope of the method, otherwise it will assume that it means they are specific to the scope of the instance.
If you think about it, it makes sense - otherwise the compiler/processor is left guessing - is this variable from the instance scope, or the method scope... do I need to go back and see if it still exists? I don't know... So I'm not sure what you mean by 'loose', but having to var your variables to declare that they are method scoped seems to be the only way I can think of to counter-act this issue. :o) HTH Mark On 5/30/05, Peter H <[EMAIL PROTECTED]> wrote: > > > > okey-dokey will do. but does that mean all variables. numbers, strings, > everything? coldfusion is beginning to seem a lot less loose than I thought > :) > > Cheers, Pete (aka lad4bear) > -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 ---------------------------------------------------------- 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]
