On Mon, Oct 26, 2009 at 2:46 AM, jdalton <john.david.dal...@gmail.com>wrote:
>
> I just wanted to point out that the pattern proposed by Andrea (http://
> bit.ly/3ePh0T)
> does in fact leak memory and will cause Safari 2 to throw a parse
> error.
quite unfair man ... first of all the warning was for this suggested code:
// custom method
jQuery.ajaxSettings.ext = (function(anonymous){
return function ext(o){
anonymous.prototype = this.data || {};
var k, result = new anonymous;
if(o){
for(k in o)
result[k] = o[k]
;
};
return result;
};
})(Function());
and I chalenge you to find a leak there where ext is the only name in that
scope.
Secondly my pattern is not a pattern, I have simply explained Internet
Explorer Scope Resolution.
You should use the web in a more productive way, leaving comments where
appropriate, as Juryi or every else does, e.g. in the related post, if your
purpose is to let people know there is something wrong, otherwise this
"blame for free" strategy becomes quite annoying, and not because your are
right, just because of the inappropriate way you do
Now again, warn somebody for above suggested code and explain in
WebReflection why there is a leak, where, and how to reproduce, thanks.
Regards
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
