clarus
Re:A blog engine written and proven in Coq
on Friday February 13, 2015 @06:09AM (#9043768)
By "system call", we do not mean "kernel call" but more "call to the system" in a broader sense, that is from the program to its environment (it could be the OS or other libraries). We should probably use another word since this is confusing.
More exactly, we check that the only calls when the user is not logged in are: ReadFile, ListPosts or Log: https://github.com/clarus/coq-chick-blog/blob/master/Spec.v#...
Re:A blog engine written and proven in Coq
on Friday February 13, 2015 @06:01AM (#9043755)
Yes, for now we assume that there is exactly one answer for each external call to the system: https://github.com/clarus/coq-chick-blog/blob/master/Spec.v#...
In practice, we should use a timeout in the implementation of all the external calls, but we did not and our model to not enforce it.
Re:Coq: The world’s best macro assembler? (2013) [pdf]
on Tuesday December 16, 2014 @07:53AM (#8756875)
Actually this is funny, because "bit" means in French the same thing as "Coq" in English. Probably to be fair we should debate about renaming "bit" also :) (or not).
Re:ProofPeer – Collaborative Theorem Proving
on Saturday November 30, 2013 @07:56AM (#6823015)
Nice project!
I wonder how does this compare to the GitHub + package manager combo. Using these tools, platforms like Ruby or Node.js became massively collaborative. To me proof development is similar to software development, so it should work as well. By the way, Coq will soon get a package manager based on OPAM: http://coq.inria.fr/cocorico/CoqDevelopment/CRGTCoq20131126?...
Aérotrain is not magnetic, it uses air resistance too. Read the link, ahem.