I agree that it seems inconsistent, but I think I can see why they did it
like this, since there are probably cases where you want to loop over all of
the *possible* arguments and do something based on that. Basically, as Mark
guessed, CF is indeed passing a null value in for that argument. A null
structure key will show up in the key list but will return false to a
StructKeyExists check, as the following code demonstrates:
<cfset myStruct = StructNew() />
<cfset StructInsert(myStruct, 'nullKey', JavaCast('null', '')) />
<cfoutput>
#StructKeyExists(myStruct, 'nullKey')#<br />
#StructKeyList(myStruct)#
</cfoutput>
On Tue, Apr 15, 2008 at 12:19 PM, Baz <[EMAIL PROTECTED]> wrote:
> I agree with your logic Matt - is the key there or not, decide - not the
> biggest headache, but still I see your point
>
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---
