Hal Murray :
> Your writeup focuses on code mutations rather than state space. (Or maybe I
> didn't read what you intended.)
Perhaps I could have been clearer. But those two problems run
together in my mind becauase of what unifies them and contrasts
with the GPSD and reposurgeon cases.
e...@thyrsus.com said:
> A lot of configuration options - even things like minsane - effectively
> change the FSM.
Right. But as you said, that's a configuration option.
> Sure, you can think of the config as part of the input state - this isn't a
> code mutation. But it also means you can
Hal Murray :
> I agree that the core FSM is complicated, but how often do we change it?
A lot of configuration options - even things like minsane - effectively change
the FSM.
Sure, you can think of the config as part of the input state - this
isn't a code mutation. But it also means you can
e...@thyrsus.com said:
> https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html
> Read that and think about it for a while. This is a very hard problem. I
> hit it and bounced.
Thanks.
>From the blog page:
> In effect, the entire logic of the sync algorithms is a gigantic free
>
