I am suggesting that article talks about standards behaviors, not part of JScript, while the one I have already posted talk about the real specific JScript situation.
In any case, having used a closure and returning back the single function in that closure there won't be a problem in any browser while with common browsers (not IE) the function will be named. It's extremely general and pointless to say: be careful about named functions ... what does it mean be careful? There is nothing to be careful about in my example, as example. It is, in any case, good to learn more about that argument that's why kangax article first and mine about IE scope resolution after could help (plus some other deeper article around the net, just be sure it's not that dated) Regards On Sun, Oct 25, 2009 at 3:04 PM, Shade <get...@gmail.com> wrote: > > @andrea -- are you suggesting that the article referenced above is > wrong and there is not a memory leak problem with IE and named > function expressions? > > I know of some code and research that seems to prove otherwise, that > is in fact an issue to be concerned about. > > > > On Oct 24, 9:19 pm, Andrea Giammarchi <andrea.giammar...@gmail.com> > wrote: > > On Sun, Oct 25, 2009 at 2:17 AM, Andrea Giammarchi < > > > > andrea.giammar...@gmail.com> wrote: > > > > > oh no, again ... kangaaaaaaaaaaaaaaaaaaax!!! > > > > this comment was just to inform you there is absolutely _nothing_ > dangerous > > or wrong in my suggestion and it will work with every bloody browser ;-) > > > > 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 -~----------~----~----~----~------~----~------~--~---
