On Feb 17, 4:46 am, Jason Mulligan <[email protected]> wrote: > On Feb 16, 12:58 pm, Andraž Kos <[email protected]> wrote: > > "Only unmaintainable code has related variables nested in a mess of > > various depth." > > Man, if only that was true... have you seen the shit that ExtJS > generates? Lots of power, lots of bad objects.
It is unlikely that a complex data structure for general use will suit every case where that data might be used. If you don't use such objects much, then getter and setter functions can help. They are also good if the data structure changes so all access to particular properties can be updated in a single getter or setter function. If you access the data alot, then it might make sense to reorganise it into a more efficient structure for your particular case. This issue has been around as long as people have been sending data to essentially unknown clients, which goes back to the early days of Electronic Data Interchange (EDI) at least (early 1970s). -- Rob -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
