>Yup. Very easy. Call any Java method And look how well CF handles *those* situations. Anyway, that's a bit of a contrivance, and only goes to further demonstrate that CF doesn't handle nulls very well, as one has to stoop (only in the sense it lies below CF) to using Java to effect your answer. So it's a bit at odds to set a variable to be one *by design* (esp as it shouldn't be setting it in the first place!).
There's a much easier example, though: <cfset a = arrayNew(1)> <cfset a[2] = "something"> A[1] is null. Again... CF handles that situation *really* well, if you try to test that value (witness various attempts at writing arrayIsDefinedAt() functions on various CF sites (cflib, etc)). I think what the other poster might have meant is something like: <cfset var myVar> This is of little use in CF, other than we're forced to init our local variables at the top of functions (a good thing!), but often it's not most appropriate to give them a default value. Adam ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
