Search the archives!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Javascript] Memory leaks?
- From: mdougherty at pbp.com (Mike Dougherty)
- Subject: [Javascript] Memory leaks?
- Date: Mon Apr 24 20:46:34 2006
Is it better to incorporate someone's library to manage closures, or to re-implement your code so that closures are not required? If you can make a strong enough case of why a closure is unavoidable, then I would suggest that you already understand the nature of the problem well enough to be able to execute your own closure management. In every case where I have suspected that my problem is related to a scope problem that would be easily solved using a closure I have found that it is easier to eliminate the dependance on the closure than to write my own closure management code. (I dislike using others' code that I do not understand well) ... just a thought. On Mon, 24 Apr 2006 21:21:18 -0400 Steve Clay <sclay@xxxxxxx> wrote: > Monday, April 24, 2006, 5:09:50 AM, Laurent wrote: >> http://laurens.vd.oever.nl/weblog/items2005/closures/ > > Every link off of this page (including fixes) locked up Opera 8.5/XP. > Anyone one else? > > Steve > -- > http://mrclay.org/ > > _______________________________________________ > Javascript mailing list > Javascript@xxxxxxxxxx > https://lists.LaTech.edu/mailman/listinfo/javascript > > > > __________________________________________________________ > This message was scanned by ATX > 9:17:43 PM ET - 4/24/2006
- References:
- [Javascript] Memory leaks?
- From: Scott Reynen
- [Javascript] Memory leaks?
- From: Laurent Muchacho
- [Javascript] Memory leaks?
- From: Steve Clay
- [Javascript] Memory leaks?
- Prev by Date: [Javascript] Memory leaks?
- Next by Date: [Javascript] Check boxs and table row back ground colors
- Previous by thread: [Javascript] Memory leaks?
- Next by thread: [Javascript] window.close () not catched
- Index(es):