Hm, looks like no one has an answer for this? ;-) I think I have to avoid such mixed access methods in future, but is this a bug in build or or isn't it?
Cheers Torsten westor wrote: > > I'm not shure if this is a bug in build optimization: > Sometimes I use an array like an object. > var result = new Array(); > var result.ACL = new Array(); > Often I access the properties (or lets say, the keys) in this way: > alert(result.ACL.propertyName); > Now I have one case, that a key name is "class" and that may lead to an > error, therefore I access it this way: > alert(result.ACL["class"]); > > That works normally well and as I understood Objects and Array, this > should work. > > When I build the application I will get a bug, at least in IE6, that ACL > (the optimized variable) is not an object or is null. And really, if I > compare: the optimized version of ACL is something different, depends on > how I access it. > One time it is $f.ACL and next it is $f.$1z - and that's really not set. > > -- View this message in context: http://www.nabble.com/build-problem-with-array---object-tf4568476.html#a13059424 Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
