On Tue, 24 Jul 2012, Martin Wittemann wrote: > Just another thought about the polyfill discussion. > I see two scenarios where problems can occur: > > 1. Some other library is adding a polyfill which is buggy. In that case, > we already will fail. Most of the static implementations map to the native > function if available so if a wrong polyfill is in place, we will fail no > matter if we supply polyfils or not. I don't see a way to get rid of that. > We want / need to rely on the native implementations.
Is it possible to detect where the "native" implementation is from? Then the feature detector could perhaps figure out if its from a (known) buggy implementation and ignore that? > Additionally to the polyfill topic we have discussed in the team here, we > also talked about the lang function which I planed to remove. Like some of > you suggested, we keep a few of them around for readability. > > qx.lang.String.contains > qx.lang.Array.min > qx.lang.Array.max > qx.lang.Array.sum > qx.lang.Array.clone Sounds good to me. Cheers, Fritz -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker +41 62 775 9900 (switch board) Aarweg 15 +41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
