English version
Accueil propos Tlchargement Ressources Contactez-nous

Ce site est rarement mis jour. Pour les informations les plus rcentes, rendez-vous sur le nouveau site OCaml l'adresse ocaml.org.

Browse thread
Recursion on React.events.
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2009-12-10 (08:39)
From: Daniel_Bünzli <daniel.buenzli@e...>
Subject: Re: Recursion on React.events.
> I still do not understand why there's the couple (tick', tick') and not
> simply tick', nevertheless...

The tick' on the left is the event you are delaying (i.e. the one you
will receive as an argument to defining function but delayed). The
tick' on the right is what you want to get out from the defining
function, here both are equal but that may not be always the case.

>> Note that in general I would avoid what you are doing altoghether by
>> providing regular_schedule as a primitive as you do for schedule. If
>> you are using too much ugly side effects and tricks in your event
>> definitions then you loose all the benefits of frp.
> Well, I do not fully agree.

In fact I retract my comment in that case. I thought you were playing
dirty tricks but in fact you were not. Sorry.

> Cool. One criticism and one question.
> Criticism: it doesn't use Calendar, which really a cool library.

I don't think you need Calendar to provide what rtime provides.

> Question: How well does Rtime interact with Lwt?

No idea I have never used Lwt.