Le 22 juin 09 à 11:19, Benjamin Canou a écrit :

> Abstract: The weak.js file remaining in the distro is a mistake. I  
> see possibilities to implement them but have no short term plans for  
> a perfect solution.

Thanks for your response. Since it allows to compile more sources  
without changes I'd leave the weak support in obrowser, but I'd make  
it clear in the documentation that so far no weak pointer will ever be  
reclaimed.

So to sum up using react in obrowser will leak, however it doesn't  
leak in "traditional" environments.

Le 22 juin 09 à 19:02, Jake Donham a écrit :

> Everything in froc happens on a "timeline". When you bind a changeable
> value, there's a chunk of the timeline that corresponds to the dynamic
> scope of the bind function. When the value changes, that chunk is
> removed, which unregisters any dependencies created in the course of
> evaluating the bind function.

But in this "chunk" can you repeatedly get external (in the sense  
primitive) input ?

Because _if_ you can't then in the breakout game example where you  
need to constantly gather (external) time and keyboards events you  
cannot "pipe" those under a single bind where you create the game  
simulation and logic signals needed  for a game run as any new  
keyboard or time event would garbage collect them. In that case the  
game signals need to be defined outside a toplevel bind and cannot be  
garbage collected by froc, it wouldn't be fixed "by wrapping  
everything in a top-level bind".

Best,

Daniel