I understand your point, but I would still expect IsDefined("thing.foo") to
return true when thing.foo = null.
Your expectation is based on languages that have a 'null' value - which CF does not.
Think of other languages (Java seems appropriate) that _do_ have a concept
of null. You can compare (thing.foo == null) for a Boolean result without
generating an exception because foo does indeed exist!
Of course - precisely because those languages have a concept of null. Since CF doesn't have such a concept, you can't expect the same behavior.
I'm not arguing whether CF should have a null added, merely stating what CF's behavior is today and explaining why that is so.
Regards, Sean
----------------------------------------------------------
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]
