steady states

1 view
Skip to first unread message

Raoul Duke

unread,
May 26, 2022, 1:46:47 PMMay 26
to pi...@googlegroups.com
in any even vaguely reactive(ish) system, how can you be sure where loops can happen? thing A changes snd observer B notices snd tells C to alter which causes C to tell A to change. 

sometimes that might well be desirable, but probably also sometimes would be kind of a bad bug. 

David Barbour

unread,
Jun 1, 2022, 5:45:24 PMJun 1
to pi...@googlegroups.com
In the common case it's very easy: loops *can* happen anywhere.

Often we're more concerned with where loops *do* happen, which might be supported via dynamic tracking. A programmer might use this information for debugging, while a program scheduler might use this information to reduce the amount of rework.

But it is feasible to design reactive systems such that dependencies and loops are subject to static analysis.

On Thu, May 26, 2022 at 12:46 PM Raoul Duke <rao...@gmail.com> wrote:
in any even vaguely reactive(ish) system, how can you be sure where loops can happen? thing A changes snd observer B notices snd tells C to alter which causes C to tell A to change. 

sometimes that might well be desirable, but probably also sometimes would be kind of a bad bug. 

--
You received this message because you are subscribed to the Google Groups "PiLuD" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pilud+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pilud/CAJ7XQb5DLa32p_dBb%2Bfbb_0Ao5QzYkLi9UPibMJJ%2BFUo0Aai_w%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages