From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Satoshi Ogasawara <ogasawara@itpl.co.jp>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] PEC ver. 1.1
Date: Tue, 17 Apr 2012 21:23:27 +0200 [thread overview]
Message-ID: <F7294E8F02FB474AA2373765B8BCAB57@erratique.ch> (raw)
In-Reply-To: <4F8D9D0E.1040007@itpl.co.jp>
Hello,
> PEC is similar to React library but there are some different points.
>
> - PEC's update cycle is separated from sending events.
> You can send a value to event during update cycle.
What's the semantics if you send two different values to an event during an update cycle ?
> - PEC doesn't hold any pointer(including weak one) to event until the
> event will be subscribed.
I'm not sure how that's different from react. If an event has no dependents (by which I understand your "subscribed"), react doesn't hold any pointer either.
> - All PEC's signal are switchable. 'switch' means you can replace dependency
> of a signal keeping signals depends on the signal unchanged.
How is that different from react's E.switch/S.switch ?
Best,
Daniel
next prev parent reply other threads:[~2012-04-17 19:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 16:40 Satoshi Ogasawara
2012-04-17 17:52 ` Adrien
2012-04-17 18:50 ` Satoshi Ogasawara
2012-04-17 19:23 ` Daniel Bünzli [this message]
2012-04-18 1:59 ` Satoshi Ogasawara
2012-04-18 7:36 ` Daniel Bünzli
2012-04-18 11:44 ` Satoshi Ogasawara
2012-04-18 13:27 ` Daniel Bünzli
2012-04-18 17:39 ` Satoshi Ogasawara
2012-04-18 22:32 ` Daniel Bünzli
2012-04-19 8:59 ` Satoshi Ogasawara
2012-04-19 10:31 ` Daniel Bünzli
2012-04-19 10:57 ` Daniel Bünzli
2012-04-19 13:31 ` Satoshi Ogasawara
2012-04-19 13:02 ` Satoshi Ogasawara
2012-04-19 14:09 ` Daniel Bünzli
2012-04-20 9:24 ` Satoshi Ogasawara
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=F7294E8F02FB474AA2373765B8BCAB57@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=ogasawara@itpl.co.jp \
/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).