Yeah, sorry I misspoke. You're right - the instances contains properties which could be objects, arrays, structs, etc. But I'm sitting in Ben Nadels jQuery preso and trying to pay attention!
On Feb 10, 2009, at 6:39 PM, Jared Rypka-Hauer wrote: > > Hrm... so you keep nested structs and CFC instances out of > variables.instance?? > > That's not how Transfer works, for example, because Transfer's > "memento" is actually a copy of the instance data for an object and > all it's composites. So if you have User.getAddressArray(), > User.getRolesArray() and User.getEmployer(), if you call > User.getMemento() you'll actually have at least 3 keys with complex > data. > > J > > On Feb 10, 2009, at 5:31 PM, Peter Bell wrote: > >> >> So the names of the instance variables don't potentially conflict >> with >> method names, and so you have a single struct you can operate on >> where >> all of the keys are simple variables, not methods or anything else. >> >> Best Wishes, >> Peter >> >> On Feb 10, 2009, at 6:28 PM, Henry wrote: >> >>> >>> Can someone remind me, why store instance variables in >>> variables.instance? Where are the benefits? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
