Arc Forumnew | comments | leaders | submitlogin
2 points by kinleyd 4859 days ago | link | parent

Nice link, @akkartik. Does offer up some options for car, cdr in Arc. Conceptually, First, Next appear to be a neater approach.


2 points by akkartik 4859 days ago | link

I'm not sure the article is directly applicable to arc (first/next mean something totally different in Lucid than say first/rest in clojure). But with such a small community I tend to share interesting links even if they aren't directly applicable.

-----

3 points by rocketnia 4859 days ago | link

You preempted my own similar reply, but I'll post it anyway. :-p

---

"Does offer up some options for car, cdr in Arc."

Whoa, really? Please share. ^_^

My reading of the article is colored by my thinking of "synchronous programming" as a programming model in which something stateful is considered to be a sequence of instantaneous values. This makes it sensible to formulate static properties of the program using a temporal logic that supports statements of the form "in the next instant it'll be true that X."

That particular benefit of synchronous programming doesn't make a whole lot of sense in Arc, where (I think) we don't often try to guarantee/inspect rich static properties of stateful models. So if you (or akkartik) see some immediate applicability to Arc, it's not obvious to me what in particular you see. ^_^

Here's the tiny little bit of work I've done with synchronous models. My goal was to find out how much this kind of model-checking technology could help when developing an interactive story, and it turned out to work very well on the toy problems I could come up with: https://github.com/rocketnia/nusmv-if

-----

2 points by kinleyd 4859 days ago | link

Heh, my comment was clearly a loose one. Remember I'm the noob here, and may be I should remind myself too. :)

-----