The best javascript engine ever — OZONE Asylum, home of the Mad Scientists

This page's ID: 28037

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	Allelujah! Here is the wonderful paper (fascinating stuff) that ties both ends, answers my question, and clarifies things. Read the part about closures, then memory leaks: [quote] http://simon.incutio.com/slides/2006/etech/javascript/js-reintroduction-notes.html [/quote] :) The origin of the issue is syntaxic, somehow: js allows for syntaxic mistakes, in that it allows closurs which can easilly produce circular references. FF's powerful gc system tries to resolve this, but it's already acting as a workaround.... In other words, classical gc, indeed, will fail at solving those references, while some other approaches will succeed. Problem? Well, the origin, indeed, is syntaxic: js's syntax allows these errors to be made. On purpose. Rhmmmm... there [b]has[/b] to be a better way. Loading...
Options:	Enable Slimies Enable Linkwords

Edit Post