Hi Creighton,<br><br>Looks like you're getting close to at least one bug. Thanks very much. Would you do me a favor and make a trac ticket, to make sure it doesn't slip through the cracks of my memory? The trac URL is <a href="http://trac.haskell.org/reactive">http://trac.haskell.org/reactive</a> .<br>
<br>If you or anyone has a suggestion or bug report to offer and doesn't want to make a trac ticket, please let me know, and I'll do it. Better yet, let me know if there's anything I can do to make it more convenient to use trac.<br>
<br>Regards, - Conal<br><br><br><br><div class="gmail_quote">2008/11/12 Creighton Hogg <span dir="ltr"><<a href="mailto:wchogg@gmail.com">wchogg@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So below is something I discovered that seems very strange.<br><br>If you run the following code as is, it will run & you'll get stuck in the already documented integral loop.<br>If you replace the use of events in main with events', the program consumes all available memory & locks up hard.<br>
<br>I know I'm horribly abusing Reactive here, but I don't see why it should fail _so_ ungracefully.<br><br>Cheers,<br>Creighton<br><br>import FRP.Reactive<br>import FRP.Reactive.LegacyAdapters<br>import Control.Concurrent<br>
import Control.Monad<br><br>x :: Event () -> Behavior Double<br>x e = b where b = integral e b<br><br>events :: Event ()<br>events = atTimes [0.1,0.2]<br><br>events' :: Event ()<br>events' = once events<br><br>
schedule a = threadDelay 100000 >> a<br><br>main = do<br> c <- makeClock<br> u <- mkUpdater (cGetTime c) (fmap print $ x events)<br> forever $ schedule u
<br>_______________________________________________<br>
Reactive mailing list<br>
<a href="mailto:Reactive@haskell.org">Reactive@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/reactive" target="_blank">http://www.haskell.org/mailman/listinfo/reactive</a><br>
<br></blockquote></div><br>