dave wrote: > You are pretty good at pointing out all the negative things so i am > kinda shocked you withheld that.
Dave, you really are overestimating the whole impact of this. The problem only really occurs when you're using closures that directly or indirectly hold on to references to native objects, creating circular references outside of the scope of the garbage collector. It's not actually that big a deal. I'd even be possible for the browser to avoid this problem altogether if a single memory allocator was used by both the ECMAScript engine and the rest of the browser, though this isn't feasible in some. Anyway, this problem is Memory Management 101. You can have memory leaks with any language. Java has them, so does ColdFusion (pre and post MX), I've noticed them with O'Caml (albeit not as much for some reason), Lua, and Python, and a host of others. Methinks the gentleman doth protest too much. K. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:197814 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
