From: Satoshi Ogasawara <ogasawara@itpl.co.jp>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] PEC ver. 1.1
Date: Thu, 19 Apr 2012 22:02:05 +0900 [thread overview]
Message-ID: <4F900CCD.5050102@itpl.co.jp> (raw)
In-Reply-To: <A9328FABD92A4920AB6703673BC7ACD6@erratique.ch>
Thank you for helping me understand with your explanation.
Your event semantics has two invariant.
1. for all e, t : occurrence of [e] at time [t] is one or zero.
2. if primitive [e] is occurred in time [t], update cycle runs in time [t].
Do you have any experience to proof a theorem against event combination term
by using above axiom and event combinators semantics? I'm interested in this
kind of reasoning.
(2012/04/19 19:31), Daniel Bünzli wrote:
> Right. But you still have to maintain some kind of mapping between the primitive event and the leaves they may influence to know which ones to update when the corresponding primitive event occurs. Do you store that in the primitive event itself or do you use a global data structure ?
Primitive events has list of leaves.
Best Regards,
Ogasawara
next prev parent reply other threads:[~2012-04-19 13:02 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
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 [this message]
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=4F900CCD.5050102@itpl.co.jp \
--to=ogasawara@itpl.co.jp \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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).