Sorry my previous comment had line-break issues. Here is my reply again. Andrea,
> quite unfair man ... first of all the warning was for this suggested code: It's perfectly fair. I linked to your exact post with the snippet (http://bit.ly/3ePh0T) > and I chalenge you to find a leak there where ext is the only name in that > scope. Just because your 1 time leak may be small doesn't mean people shouldn't be aware of it. Especially if they adopt that technique for their entire project (potentially hundreds or thousands of leaks). > Secondly my pattern is not a pattern, I have simply explained Internet > Explorer Scope Resolution. Sorry I should have used the word "snippet". > Now again, warn somebody for above suggested code and explain in > WebReflection why there is a leak, where, and how to reproduce, > thanks. Juriy's (kangax) article on function expression did a pretty good job of this already. You are promoting a snippet that causes extra memory consumption in IE. So my post let everyone know that yes, there is something wrong with your snippet and that yes they should be careful with named expressions. I am sorry if your ego was hurt. It's nothing personal, I am just stopping the misinformation. - JDD --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
