From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id 39450BC37 for ; Thu, 10 Dec 2009 09:39:29 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhwBADdCIEtKfU4akGdsb2JhbACEJZcAPwEBAQEJCQwHEwOpGoFZhUeIaQECAwWBKoIqUwSCfYgq X-IronPort-AV: E=Sophos;i="4.47,374,1257116400"; d="scan'208";a="38339649" Received: from ey-out-2122.google.com ([74.125.78.26]) by mail2-smtp-roc.national.inria.fr with ESMTP; 10 Dec 2009 09:39:29 +0100 Received: by ey-out-2122.google.com with SMTP id 22so1656548eye.7 for ; Thu, 10 Dec 2009 00:39:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=zdhg6SS738R91FoLPWPna1clQsx/Q2iY394DqEimTnw=; b=FZotS7wJzjC7wBBJ8Ivx27JvehEZFVxWM5kz2DQldlHkfMidOXub9Xj18X4wgrTWti UNMrMT8m8OxN0DaozyRQjBHARjgak8In47/kUxbMJRu2Cz0DVmhzQgHdZcrC+hpn9Bh6 1xTv8DP+lDKXxD7kHlh+vJVEANhJduqSdbh8U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=dKHkoYwT5ahhkjIqYTjqLprzXwsox3WBWLg0KH0JEpSdQkVYg7Bj1xrdNTfvo1u3aP It2+Q118RRLW+C16xDXIZsGQnoCj0vqb5cYIWSvsbiMJTv8xsS89dPnnMjOVzW48dpbZ 43hCuP5a465HWCtNTjuH3W8Ij/WudOESKOlb8= MIME-Version: 1.0 Sender: daniel.c.buenzli@gmail.com Received: by 10.213.2.82 with SMTP id 18mr11616079ebi.58.1260434368644; Thu, 10 Dec 2009 00:39:28 -0800 (PST) In-Reply-To: <4B1FF0DD.903@citycable.ch> References: <4B1F0E3A.3040907@citycable.ch> <91a3da520912082025mf4aba28o2b36884b3b001831@mail.gmail.com> <4B1FF0DD.903@citycable.ch> Date: Thu, 10 Dec 2009 16:39:28 +0800 X-Google-Sender-Auth: dd88aab532bb41e8 Message-ID: <91a3da520912100039r20989c79ka055600e41d36215@mail.gmail.com> Subject: Re: Recursion on React.events. From: =?UTF-8?Q?Daniel_B=C3=BCnzli?= To: guillaume.yziquel@citycable.ch Cc: caml-list@inria.fr Content-Type: text/plain; charset=UTF-8 X-Spam: no; 0.00; recursion:01 buenzli:01 delayed:01 argument:02 primitive:02 defining:02 defining:02 library:03 frp:04 daniel:04 daniel:04 ugly:04 function:08 function:08 delaying:10 > 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. Daniel