1. 18 Mar, 2011 2 commits
  2. 17 Mar, 2011 6 commits
  3. 16 Mar, 2011 9 commits
  4. 15 Mar, 2011 4 commits
  5. 11 Mar, 2011 3 commits
  6. 10 Mar, 2011 1 commit
  7. 09 Mar, 2011 4 commits
  8. 08 Mar, 2011 9 commits
  9. 05 Mar, 2011 2 commits
    • Andrei Paskevich's avatar
      add "stop_split" at every explanation label · 1d0c0ca6
      Andrei Paskevich authored
      The idea is that every big WP is built from "explainable" subformulas.
      So, when we split for the first time, we stop at these subformulas.
      The subsequent split will split them further.
      Note that split_goal removes "stop_split" labels. Thus, if we have
      an atomic assertion ("expl:precondition" "stop_split" true), then
      the split_goal transformation will succeed and return a _different_
      task, with the goal: ("expl:precondition" true). However, the second
      split will return the same task exactly. Should we fix it?
      At the moment, we lack explanation annotations over postconditions.
    • Andrei Paskevich's avatar
      temporarily add a module Dbsync that wraps each call to Db in a mutex · 592bb722
      Andrei Paskevich authored
      yes, this is horribly inefficient, but this is the only way I can
      actually use transformations in WhyIDE. As soon as we push all IDE
      (or at least all Db) to one thread, Dbsync can be thrown out.