syndicate-lang
/
syndicate-2017
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Guess at a place where checking of termination conditions should occur

This commit is contained in:
Tony Garnock-Jones 2015-12-03 13:45:27 -08:00
parent aae15a008b
commit bddcf9a240
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/notes-on-hll.md
View File

@ -74,9 +74,11 @@ This is leading me to believe that the order of operations is:
- update `track`s and assertion-sets related to `rising-edge`.
- handle `on` for `asserted`, `retracted` and `rising-edge`, in order of appearance (!?)
- maintain `assert`s
- check termination conditions
- Given a message,
- handle `on` for `message` and `rising-edge`, in order of appearance (!?)
- maintain `assert`s
- check termination conditions
Actually, I'm not sure `falling-edge` is encodable using
`rising-edge`, since the initial state might be different. Do we