You wouldn't name your own keys this way - on the other hand it's good to know CF can cope with these types of keys if you're writing caching code or something else where you want to associate arbitrary string keys with a value (although I'd probably hash() the string first for good luck).
People who've done a CF course with me know that I always try to use structKeyExists() over isDefined() - I use the latter when I need to check that some deeply nested key exists without having to check all the intermediate keys along the way. Robin Robin Hilliard CEO - RocketBoots Pty Limited Consulting . Recruitment . Software Licensing . Training http://www.rocketboots.com.au m +61 418 414 341 e [EMAIL PROTECTED] On 06/06/2007, at 7:14 AM, Simon Haddon wrote: > It is the sort of thing you don't want to teach your developers as > I can imagine the heartache that would cause. > > On 06/06/07, David Harris < [EMAIL PROTECTED]> wrote: > > you can do this (as per my example code): > <cfset myStruct["some value here"] = "bob"> > > try this one: > > <cfset myStruct = structNew()> > <cfset myStruct["some.value.here and a space too, and an > [EMAIL PROTECTED]"] = "fred"> > <cfdump var="#myStruct#"> > > > it's one of those things that *can* be done, but (as rule of thumb) > isn't... > > but if you do, It'll break "isDefined()" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
