Yes, this is exactly what's happening. CF has a concept of NULL (otherwise how would cfdump spit out "undefined struct element"), it just likes to throw errors before allowing you to test for it.
Basically, I have arrived at if structkeyExists() == true and assigning the value into a dummy var errors, then it's null. Talk about overhead...
Hmm, that doesn't really make sense to me. If thing.foo is null then isDefined("thing.foo") should be *false* even tho' structKeyExists(thing,"foo") is true. Can you show a reproducible example of what you're seeing?
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]
