caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Obj.magic and existential types.
Date: Tue, 23 Jun 2009 02:24:22 +0200	[thread overview]
Message-ID: <66E06129-1281-48F4-AE9D-E56FD716917A@erratique.ch> (raw)
In-Reply-To: <c7e4e9f0906221002l57e444dgd146cbcb616c193@mail.gmail.com>

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

  reply	other threads:[~2009-06-23  0:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 17:42 Guillaume Yziquel
2009-06-19 18:21 ` Daniel Bünzli
2009-06-19 18:30   ` Guillaume Yziquel
2009-06-19 18:37     ` Daniel Bünzli
2009-06-19 18:47   ` [Caml-list] " Jake Donham
2009-06-20  8:30     ` Daniel Bünzli
2009-06-21 18:08       ` Jake Donham
2009-06-21 18:39         ` Yaron Minsky
2009-06-22  0:03         ` Daniel Bünzli
2009-06-22  9:19           ` Benjamin Canou
2009-06-22 17:02           ` Jake Donham
2009-06-23  0:24             ` Daniel Bünzli [this message]
2009-06-23  0:34               ` Jake Donham
2009-06-23  2:22               ` Jake Donham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=66E06129-1281-48F4-AE9D-E56FD716917A@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).