Some memory leaks are so noticeable that js devs are forced to worry about things that would normally be ignored. Killing circular references is nowadays, a common burden on js devs.
Same goes for string concatenation (being forced to use arrays on IE), annoying! That's life Cheers -- Ariel Flesler http://flesler.blogspot.com/ On Oct 21, 1:14 pm, "Andrea Giammarchi" <[EMAIL PROTECTED]> wrote: > The good part of garbage collector based programming languages is that > developers should not be worried about "in core" memory problems as these > should not exist. > > More than code clearly trying to delete what is deletable and to avoid > unnecessary "chain leaks", I presume there are few things we can do, since > we cannot force the "lower level engine" to do tasks it has not being > designed for ( ... sorry guys, I guess I have a leak with my English as well > ... so even if you use best grammar in this topic, I cannot guarantee I'll > reply properly ... ) > > Kind Regards > > On Tue, Oct 21, 2008 at 3:52 PM, Fabien Meghazi <[EMAIL PROTECTED]> wrote: > > I would like to see someone with strong knowledge about memory leaks > > writing best practice jquery coding in order to avoid memory leaks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
