I don't really know what the "usual" order is, but key,value seems a lot more natural to me than value,key. After all, key=>value is always well defined while value doesn't necessarily map to a single key.
Cheers, Fritz Fritz Zaucker Oetiker+Partner AG Aarweg 15 CH-4600 Olten +41 62 775 9903 > Am 17.10.2014 um 16:32 schrieb Peter Schneider <p.schnei...@tis-gmbh.de>: > > While we are at this topic: > > I've just stepped into another 'inconsistency': > > The 'forEach' methods of the Storage Classes[1] all call the callback function > with a 'switched' parameter signature. > > Normally forEach-method callbacks have a signature of: > function (value, key, context) > while the storage-classes forEach-method callbacks have a signature of: > function (key, value) > > This is not nice and unexpected, too ;) > > Regards, > Peter > > ----------------- > [1] qx.bom.Storage.Web#forEach > qx.bom.Storage.Memory#forEach > qx.bom.Storage.UserData#forEach // O.K. IE <8 is not really needed ;) > > > >> Am 10/17/2014 um 12:46 PM schrieb d...@cost-savers.net: >> I will gladly do! >> >> Stefan >> >>> Hi Stefan, >>> >>> You're right. This framework is growing over the last years with help of >>> many developers >>> with different paradigms and "styles" of programming. >>> >>> But with your help and the help of the community we can reach the goal to >>> improve these interfaces >>> to become more heterogeneous. To reach this goal much faster we would be >>> very happy >>> if you send us pull requests to improve qooxdoo :) >>> >>> If you have questions about the pull request process don't hesitate to ask >>> us. >>> >>> Have a nice weekend >>> Cheers Tobias >>> >>> >>> >>> -----Ursprüngliche Nachricht----- >>> Von: d...@cost-savers.net [mailto:d...@cost-savers.net] >>> Gesendet: Donnerstag, 16. Oktober 2014 21:21 >>> An: qooxdoo-devel@lists.sourceforge.net >>> Betreff: [qooxdoo-devel] Heterogeneous code in Interfaces? >>> >>> Is there any reason why the type checking and parameter counting of >>> Interfaces are heterogeneous? >>> >>> In some classes >>> >>> arguments.length == 1 >>> >>> and others >>> >>> this.assertArgumentsCount(arguments, 1, 1); >>> >>> are used. >>> >>> Furthermore, in some >>> >>> no type checking when incoming parameters of functions/methods >>> >>> in others >>> >>> this.assertInteger(month); >>> >>> >>> Shouldn't all implement the assert functions? >>> >>> >>> Stefan > > -- > > ** Unsere Veranstaltungen: > > 3. Innovationsforum Telematik in Bocholt, 16.10.2014 > BWVL-Tagung in Köln, 12.-13.11.2014 > > ** NEU: Unser BLOG: > > telematics-magazine.com > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
